June 2012 - macports-tickets - lists.macosforge.org

[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] #34429: OpenSSL version mismatch. Built against 1000101f, you have 1000005f
by MacPorts 16 Feb '14

16 Feb '14

#34429: OpenSSL version mismatch. Built against 1000101f, you have 1000005f --------------------------------+------------------------------------------- Reporter: conradwt@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Keywords: lion | Port: openssh --------------------------------+------------------------------------------- I'm seeing the following issue when trying to use ssh: {{{ $ ssh username@host OpenSSL version mismatch. Built against 1000101f, you have 1000005f }}} I have the following versions of openssh and openssl installed: {{{ $ port installed openssh The following ports are currently installed: openssh @5.9p1_3 (active) [17:25] [~/.ssh] [ruby] [1.9.2] $ port installed openssl The following ports are currently installed: openssl @1.0.1c_0 (active) }}} Last but not least, I have tried uninstalling and installing openssl but I'm still getting the above message. -- Ticket URL: <https://trac.macports.org/ticket/34429> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[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

[MacPorts] #33370: wget should use curl-ca-bundle by default
by MacPorts 10 Feb '14

10 Feb '14

#33370: wget should use curl-ca-bundle by default -------------------------------+-------------------------------------------- Reporter: dave@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: -------------------------------+-------------------------------------------- I think you're going to see this same issue applies in a lot of places. Now that it's been fixed for svn (see #19247), could we fix it for wget and everything else too? {{{ pluto:/tmp dave% wget https://raw.github.com/gist/1746342/702dfe9e2dd79fddd536aa90d561efdeec2ba716 --2012-02-27 08:14:17-- https://raw.github.com/gist/1746342/702dfe9e2dd79fddd536aa90d561efdeec2ba716 Resolving raw.github.com (raw.github.com) 207.97.227.243 Connecting to raw.github.com (raw.github.com)|207.97.227.243|:443... connected. ERROR: The certificate of `raw.github.com' is not trusted. ERROR: The certificate of `raw.github.com' hasn't got a known issuer. pluto:/tmp dave% curl -O https://raw.github.com/gist/1746342/702dfe9e2dd79fddd536aa90d561efdeec2ba716 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 7341 100 7341 0 0 4875 0 0:00:01 0:00:01 --:--:-- 15821 pluto:/tmp dave% }}} -- Ticket URL: <https://trac.macports.org/ticket/33370> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #34444: klavaro 1.8.1 Install error - build failure
by MacPorts 10 Feb '14

10 Feb '14

#34444: klavaro 1.8.1 Install error - build failure ------------------------------------+--------------------------------------- Reporter: vincent.oberson@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Keywords: | Port: klavaro ------------------------------------+--------------------------------------- Hi, Installation of klavaro fails during build process: {{{ :info:build Undefined symbols for architecture x86_64: :info:build "_g_module_supported", referenced from: :info:build _main in main.o }}} MacPorts and Xcode are newly installed (yesterday evening). I'm running MacOS X Lion 10.7.3 and Xcode 4.3.2. "main.log" file is attached to this message. Thanks in advance for your help! -- Ticket URL: <https://trac.macports.org/ticket/34444> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5