October 2011 - macports-tickets - lists.macosforge.org

[MacPorts] #26472: Add extra variants to postgresql90
by MacPorts 22 Feb '14

22 Feb '14

#26472: Add extra variants to postgresql90 -----------------------------------+---------------------------------------- Reporter: ddebernardy@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: postgresql90 -----------------------------------+---------------------------------------- Similarly to #24684, there are a whole bunch of contrib modules in pgsql90 which aren't available when installing it using macports, and which would be really sweet -- either by default, or as variants. In particular the unaccent contrib. Alternatively, could there be a postgresql90-contrib package that bulk installs each and every one of them? Most people, I'm assuming, use macports on their laptops for local development, making it no big deal if more than what's strictly necessary gets installed. -- Ticket URL: <http://trac.macports.org/ticket/26472> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7

[MacPorts] #18085: p5-mail-spamassassin fails to install
by MacPorts 22 Feb '14

22 Feb '14

#18085: p5-mail-spamassassin fails to install ----------------------------------+----------------------------------------- Reporter: olaf@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: perl5.8 spamassassin | Port: p5-mail-spamassassin ----------------------------------+----------------------------------------- During the installation the following is logged: {{{ ---> Fetching p5-mail-spamassassin ---> Attempting to fetch Mail-SpamAssassin-3.2.5.tar.gz from http://www.mirrorservice.org/sites/ftp.cpan.org/pub/CPAN/modules/by- module/Mail ---> Verifying checksum(s) for p5-mail-spamassassin ---> Extracting p5-mail-spamassassin ---> Configuring p5-mail-spamassassin ---> Building p5-mail-spamassassin ---> Staging p5-mail-spamassassin into destroot Error: Target org.macports.destroot returned: error renaming "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_perl_p5 -mail- spamassassin/work/destroot/opt/local/etc/mail/spamassassin/init.pre": no such file or directory Error: Status 1 encountered during processing. }}} -- Ticket URL: <http://trac.macports.org/ticket/18085> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #16690: add db46 support for p5-mail-spamassassin
by MacPorts 22 Feb '14

22 Feb '14

#16690: add db46 support for p5-mail-spamassassin ------------------------------------+--------------------------------------- Reporter: 13z73rch3un9(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Keywords: db46 spamassassin | Port: p5-mail-spamassassin ------------------------------------+--------------------------------------- It would be nice to have support for db46 support for bayesian filters db with spamassassin. How to reproduce: * copy $HOME/.spamassassin/bayes_toks from a reasonably up-to-date linux machine * file(1) should identify the file as "Berkeley DB (Hash, version 9, little-endian)" * running ``spamassassin < /dev/null'' will return the following: [2274] warn: bayes: cannot open bayes databases /Users/lester/.spamassassin/bayes_* R/O: tie failed: Inappropriate file type or format [2274] warn: bayes: cannot open bayes databases /Users/lester/.spamassassin/bayes_* R/O: tie failed: Inappropriate file type or format FYI, if you create the file (by running sa-learn and feed something to it) you will get a file in "Berkeley DB 1.85 (Hash, version 2, native byte- order)" format. Again, as reported by file(1). Seems this is created by using the Perl DB_File module... -- Ticket URL: <http://trac.macports.org/ticket/16690> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #25976: Add OTR Support to Weechat
by MacPorts 21 Feb '14

21 Feb '14

#25976: Add OTR Support to Weechat --------------------------------+------------------------------------------- Reporter: frenchja@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: weechat otr | Port: weechat --------------------------------+------------------------------------------- The instructions available here (http://wiki.flashtux.org/wiki/WeeChat /irc-otr) don't compile the libotr plugin for Weechat. It results in the log attached. It would be great if we could add in +otr as a configuration option. I apologize but I really can't understand the log or I'd add more detail. -- Ticket URL: <http://trac.macports.org/ticket/25976> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #26208: WeeChat 0.3.2 double plugins
by MacPorts 21 Feb '14

21 Feb '14

#26208: WeeChat 0.3.2 double plugins -----------------------------------+---------------------------------------- Reporter: f.p.verhoog@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: plugins | Port: weechat -----------------------------------+---------------------------------------- in the plugins folder of weechat "/opt/local/lib/weechat/plugins/" are symlinks of the original plugins '''and''' the original plugins. Like symlink "alias.so" and the plugin "alias.0.so". wich gives errors at startup of weechat. the symlinks should be removed or the plugins should be in another folder. -- Ticket URL: <http://trac.macports.org/ticket/26208> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #27798: bad default $PATH for sshd
by MacPorts 16 Feb '14

16 Feb '14

#27798: bad default $PATH for sshd ---------------------------------+------------------------------------------ Reporter: vinc17@… | Owner: jwa@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: openssh ---------------------------------+------------------------------------------ /opt/local/etc/ssh/sshd_config contains: {{{ # This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin:/opt/local/bin }}} and indeed: {{{ % ssh -p 2222 localhost echo \$PATH /usr/bin:/bin:/usr/sbin:/sbin:/opt/local/bin }}} IMHO, /opt/local/bin should come first so that versions provided by MacPorts are preferred. Otherwise {{{ % ssh -p 2222 localhost rsync --version rsync version 2.6.9 protocol version 29 }}} instead of the rsync provided by MacPorts. Adding the configure option {{{ --with-default-path=${prefix}/bin:/usr/bin:/bin:/usr/sbin:/sbin }}} would solve the problem. -- Ticket URL: <https://trac.macports.org/ticket/27798> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #19481: openssl: integration with OS X keychain broken
by MacPorts 16 Feb '14

16 Feb '14

#19481: openssl: integration with OS X keychain broken -----------------------------------+---------------------------------------- Reporter: lhunath@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.7.1 Keywords: openssh ssh-agent ssh | Port: -----------------------------------+---------------------------------------- It appears that one of the more recent updates of openssl has broken its integration with the OS X keychain. My SSH keys that are in the OS X keychain are no longer added to the ssh-agent. Running `eval "$(/usr/bin/ssh-agent)"` and then `ssh-add -l` *does* show my keys as added to the agent, so the OS X provided openssl has no issues talking to my keychain. That makes macports' openssl rather useless for me. This issue is reminiscent of another open ticket on sysutils/screen which also causes problems with interaction between CLI applications and the OS X keychain (and other OS X utilities such as pbcopy/pbpaste): #18235 -- Ticket URL: <http://trac.macports.org/ticket/19481> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #16201: Upgrading openssh overwrites user-modified config files
by MacPorts 16 Feb '14

16 Feb '14

#16201: Upgrading openssh overwrites user-modified config files ---------------------------------+------------------------------------------ Reporter: vinc17(a)macports.org | Owner: wms(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: | ---------------------------------+------------------------------------------ The openssh port shouldn't overwrite user-modified config files (ssh_config and sshd_config), or should introduce some mechanism to do config file upgrades safely. For instance, contents between some markers could be preserved, e.g. {{{ # BEGIN local configuration ... # END local configuration }}} In such a case, such configuration should be near the beginning of the file. The ssh_config man page says: {{{ For each parameter, the first obtained value will be used. The configu- ration files contain sections separated by ``Host'' specifications, and that section is only applied for hosts that match one of the patterns given in the specification. The matched host name is the one given on the command line. Since the first obtained value for each parameter is used, more host- spe- cific declarations should be given near the beginning of the file, and general defaults at the end. }}} I don't know about sshd_config. I suppose that the same rule is applied. -- Ticket URL: <http://trac.macports.org/ticket/16201> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #27730: gst 3.2.3
by MacPorts 16 Feb '14

16 Feb '14

#27730: gst 3.2.3 -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: saispo@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: gst -------------------------------------+-------------------------------------- gst 3.2.3 is available so the gst port should probably be updated to that version. -- Ticket URL: <https://trac.macports.org/ticket/27730> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #15939: port install : in need of a progressbar
by MacPorts 14 Feb '14

14 Feb '14

#15939: port install : in need of a progressbar --------------------------------------+------------------------------------- Reporter: pc(a)anykey.de | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Low | Milestone: Component: base | Version: 1.6.0 Keywords: port install progressbar | --------------------------------------+------------------------------------- Installing bigger Distributions, like texlive_texmf-full (>125MB), I was wondering if everything is allright after some minutes of nothingness. I know that other *nix-packet-managers have a progressbar (some dots or whatever) so that the user is able to track the progress, at least having an idea if everything is allright. Since now I know I just have to wait, everything is fine for me. Thinking of other users - they would sometimes appreciate to have a progressbar when installing using port, I suppose. Thinking of gentoo-users sitting next to me, I would appreciate that anyway ;) -- Ticket URL: <http://trac.macports.org/ticket/15939> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7