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

[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] #36528: dmapd @0.0.45 build fails
by MacPorts 21 Feb '14

21 Feb '14

#36528: dmapd @0.0.45 build fails ----------------------+-------------------------------- Reporter: pdvsfh@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: ----------------------+-------------------------------- {{{osx 10.7, xcode 4.5.1, macport-lion 2.1.2, see also ticket 32350}}} after fix #32350 dmapd worked fine. after a few months i stopped using it. now i want it again, and before installing dmapd on another mac running mountain lion i'm trying to reinstall on lion. build fails. {{{port clean dmapd && port -dv install dmapd}}} -- Ticket URL: <https://trac.macports.org/ticket/36528> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #35944: gtk3: universal variant fails
by MacPorts 19 Feb '14

19 Feb '14

#35944: gtk3: universal variant fails -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: cal@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: gtk3 -------------------------------------+-------------------------------------- {{{:error:destroot org.macports.destroot for port gtk3 returned: /opt/local/lib/girepository-1.0/Gtk-3.0.typelib differs in /opt/local/var/macports/build/_Users_rschmidt_macports_dports_gnome_gtk3/gtk3/work/destroot-i386 and /opt/local/var/macports/build/_Users_rschmidt_macports_dports_gnome_gtk3/gtk3/work /destroot-x86_64 and cannot be merged}}} -- Ticket URL: <https://trac.macports.org/ticket/35944> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #36568: mysql @5.5.27 build failure error: incomplete definition of type 'struct st_mysql_lex_string'
by MacPorts 17 Feb '14

17 Feb '14

#36568: mysql @5.5.27 build failure error: incomplete definition of type 'struct st_mysql_lex_string' --------------------------+-------------------------------- Reporter: misc@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: mountainlion | Port: MySQL 5.5 --------------------------+-------------------------------- On Mac OS X 10.8.2 with Xcode 4.5.1 the build of mysql server 5.5 fails. Command used to install {{{ sudo port install mysql55-server ---> Computing dependencies for mysql55-server ---> Dependencies to be installed: mysql55 ---> Fetching archive for mysql55 ---> Attempting to fetch mysql55-5.5.27_0.darwin_12.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/mysql55 ---> Attempting to fetch mysql55-5.5.27_0.darwin_12.x86_64.tbz2 from http://lil.fr.packages.macports.org/mysql55 ---> Attempting to fetch mysql55-5.5.27_0.darwin_12.x86_64.tbz2 from http://packages.macports.org/mysql55 ---> Fetching distfiles for mysql55 ---> Attempting to fetch mysql-5.5.27.tar.gz from http://ftp.plusline.de/mysql/Downloads/MySQL-5.5/ ---> Verifying checksum(s) for mysql55 ---> Extracting mysql55 ---> Applying patches to mysql55 ---> Configuring mysql55 ---> Building mysql55 Error: org.macports.build for port mysql55 returned: command execution failed Error: Failed to install mysql55 Please see the log file for port mysql55 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_databases_mysql55/mysql55/main.log Error: The following dependencies were not installed: mysql55 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port mysql55-server failed }}} Build error that starts with {{{ 10: error: incomplete definition of type 'struct st_mysql_lex_string' lex_str->str= (char *) c_str; ~~~~~~~^ /opt/local/include/mysql/plugin.h:47:16: note: forward declaration of 'struct st_mysql_lex_string' typedef struct st_mysql_lex_string MYSQL_LEX_STRING; ^ In file included from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_databases_mysql55/mysql55/work/mysql-5.5.27/mysys/array.c:19: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_databases_mysql55/mysql55/work/mysql-5.5.27/include/m_string.h:295:10: error: incomplete definition of type 'struct st_mysql_lex_string' }}} See attached log file for complete error message. It looks like this could be related to some other similar reported errors on other ports: [https://trac.macports.org/search?q=incomplete+definition+of+type&noquickjum…] -- Ticket URL: <https://trac.macports.org/ticket/36568> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[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