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

[MacPorts] #35094: p5.12-xml-parser fails to replace p5-xml-parser during wine install attempt
by MacPorts 06 Jul '12

06 Jul '12

#35094: p5.12-xml-parser fails to replace p5-xml-parser during wine install attempt --------------------------------------+------------------------------------- Reporter: tamez_flores@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.1.1 Keywords: | Port: --------------------------------------+------------------------------------- {{{ NullMac:~ MiJA2010$ sudo port install wine ---> p5-xml-parser is replaced by p5.12-xml-parser ---> Computing dependencies for p5.12-xml-parser ---> Cleaning p5.12-xml-parser ---> Computing dependencies for wine ---> Applying patches to wine Error: org.macports.patch for port wine returned: command execution failed Please see the log file for port wine for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_wine/wine/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port wine failed NullMac:~ MiJA2010$ sudo port install wine @1.4.1 ---> p5-xml-parser is replaced by p5.12-xml-parser ---> Computing dependencies for p5.12-xml-parser ---> Cleaning p5.12-xml-parser ---> Computing dependencies for wine ---> Applying patches to wine Error: org.macports.patch for port wine returned: command execution failed Please see the log file for port wine for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_wine/wine/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port wine }}} Occurred on Mac OSX Lion 10.7.4 Latest Xcode Version -- Ticket URL: <https://trac.macports.org/ticket/35094> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #35086: Ports py26-ngl and py26-nio failing on fetch of ncl_ncarg-6.0.0.tar.gz
by MacPorts 06 Jul '12

06 Jul '12

#35086: Ports py26-ngl and py26-nio failing on fetch of ncl_ncarg-6.0.0.tar.gz -------------------------------+-------------------------------------------- Reporter: wdc.csa@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Keywords: ncarg | Port: py26-ngl -------------------------------+-------------------------------------------- Macports: Ports py26-ngl and py26-nio are failing on installation and subsequent fetch of ncl_ncarg-6.0.0.tar.gz -- ncarg does not appear to be available from any of the mirror sites tested by the installation procedure. The log file from the ncarg install is attached. Thanks for investigating this issue. -- Ticket URL: <https://trac.macports.org/ticket/35086> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #30094: iTerm2: Sparkle is enabled
by MacPorts 05 Jul '12

05 Jul '12

#30094: iTerm2: Sparkle is enabled ---------------------------------+------------------------------------------ Reporter: raimue@… | Owner: singingwolfboy@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: iTerm2 ---------------------------------+------------------------------------------ The iTerm2 port provides an iTerm2.app which uses the Sparkle framework. Sparkle is a framework which is used for updating an application from within the application itself (see the "Check for update..." entry in the menu). In our case, we don't want auto-updates. MacPorts has to be used for updating to a newer version and for replacing the application bundle. Therefore we have to patch iTerm2 to remove Sparkle or at least find a way to disable its invocation. -- Ticket URL: <https://trac.macports.org/ticket/30094> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #23913: allow selective enabling of bash-completion modules
by MacPorts 05 Jul '12

05 Jul '12

#23913: allow selective enabling of bash-completion modules ---------------------------------+------------------------------------------ Reporter: jabronson@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Keywords: | Port: ---------------------------------+------------------------------------------ Currently there is no way to selectively enable bash-completion modules; "{{{. /opt/local/etc/bash_completion}}}" causes all 149 modules in {{{/opt/local/etc/bash_completion.d}}} to be loaded and results in an unnecessary slowdown in shell startup time (e.g. 0.635s on my new Macbook Pro when the disk cache is cold (0.224s when hot)). Other bash-completion distributions provide a facility for selectively enabling modules (e.g. {{{eselect bashcomp enable ...}}} on Gentoo). Could MacPorts make use of their prior art somehow? -- Ticket URL: <http://trac.macports.org/ticket/23913> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #35090: Running bash_completion script is slow, due to have() function
by MacPorts 05 Jul '12

05 Jul '12

#35090: Running bash_completion script is slow, due to have() function ------------------------------------+--------------------------------------- Reporter: justin.lebar@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Keywords: | Port: ------------------------------------+--------------------------------------- {{{ $ time bash /opt/local/etc/bash_completion real 0m2.954s user 0m0.078s sys 0m0.037s }}} If I modify the have() function so it returns 0 (instead of running |type|) I get {{{ $ time bash /opt/local/etc/bash_completion real 0m0.245s user 0m0.059s sys 0m0.010s }}} I'm totally in favor of not loading complex completion scripts for commands that aren't installed, but that doesn't appear to be what's happening here; have() guards only very basic completion for some commands, afaict. Making opening a new terminal window 10x slower for the sake of avoiding some |complete| calls seems like a premature optimization and a bad trade- off. -- Ticket URL: <https://trac.macports.org/ticket/35090> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #34580: phppgadmin: update to 5.0.4
by MacPorts 05 Jul '12

05 Jul '12

#34580: phppgadmin: update to 5.0.4 -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: miwi@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: phppgadmin -------------------------------------+-------------------------------------- -- Ticket URL: <https://trac.macports.org/ticket/34580> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #35091: Invalid Allegro4/Allegro5 Conflict
by MacPorts 05 Jul '12

05 Jul '12

#35091: Invalid Allegro4/Allegro5 Conflict -----------------------------------------+---------------------------------- Reporter: luiji@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.1.1 Keywords: conflict, package, allegro | Port: allegro, allegro5 -----------------------------------------+---------------------------------- The allegro and allegro5 packages say that they conflict, but they shouldn't. Allegro 5.x was specifically designed so that the two packages would not conflict, and I have vanilla installations of them both installed on my Linux machines without any problems. I marked this as high-priority because there are a number of games depending on 4 and a number on 5, and if this invalid conflict persists then they won't be able to co-exist. -- Ticket URL: <https://trac.macports.org/ticket/35091> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #34494: Problems installing hdf5 with new version of Macports
by MacPorts 05 Jul '12

05 Jul '12

#34494: Problems installing hdf5 with new version of Macports ----------------------------------+----------------------------------------- Reporter: steeves@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.0 Keywords: rev-update hdf5 | Port: hdf5 ----------------------------------+----------------------------------------- Starting from fresh install, running "port install hdf5" fails with Error: Port hdf5 is still broken after rebuiling it more than 3 times. Error: Please run port -d -y rev-upgrade and use the output to report a bug. Port hdf5 still broken after rebuilding 3 time(s) while executing "error "Port $portname still broken after rebuilding [expr $broken_port_counts($portname) - 1] time(s)"" (procedure "revupgrade_scanandrebuild" line 240) invoked from within "revupgrade_scanandrebuild broken_port_counts $opts" (procedure "macports::revupgrade" line 5) invoked from within "macports::revupgrade $opts" (procedure "action_revupgrade" line 2) invoked from within "action_revupgrade $action $portlist $opts" (procedure "action_target" line 94) invoked from within "$action_proc $action $portlist [array get global_options]" (procedure "process_cmd" line 95) invoked from within "process_cmd $remaining_args" invoked from within "if { [llength $remaining_args] > 0 } { # If there are remaining arguments, process those as a command set exit_status [process_cmd $remaining..." (file "/opt/local/bin/port" line 4784) [steevmi1@phusca-l24500][20:27] [~/] % sudo port -d -y rev-upgrade Password: DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/bugpoint DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llc DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/lli DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-ar DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-as DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-bcanalyzer DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-cov DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-diff DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-dis DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-dwarfdump DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-extract DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-ld DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-link DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-mc DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-nm DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-objdump DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-prof DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-ranlib DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-rtdyld DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-size DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/macho-dump DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/opt DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/ld64/ld DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-2.9/bin/bugpoint DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-2.9/bin/llc DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-2.9/bin/lli DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-2.9/bin/llvm-ar DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-2.9/bin/llvm-as DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-2.9/bin/llvm-bcanalyzer DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-2.9/bin/llvm-diff DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-2.9/bin/llvm-dis DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-2.9/bin/llvm-extract DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-2.9/bin/llvm-ld DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-2.9/bin/llvm-link DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-2.9/bin/llvm-mc DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-2.9/bin/llvm-nm DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-2.9/bin/llvm-objdump DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-2.9/bin/llvm-prof DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-2.9/bin/llvm-ranlib DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-2.9/bin/llvmc DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-2.9/bin/macho-dump DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-2.9/bin/opt ---> Scanning binaries for linking errors Could not open /opt/local/lib/libh5test.0.dylib: Error opening or reading file (referenced from /opt/local/bin/h5perf) DEBUG: Marking /opt/local/bin/h5perf as broken ---> Found 1 broken file(s), matching files to ports ---> Found 1 broken port(s), determining rebuild order DEBUG: Processing port hdf5 @0:1.6.9_1 ---> Rebuilding in order hdf5 @1.6.9 DEBUG: epoch: in tree: 0 installed: 0 DEBUG: hdf5 1.6.9_1 exists in the ports tree DEBUG: hdf5 1.6.9_1 is the latest installed DEBUG: hdf5 1.6.9_1 is active DEBUG: Merging existing variants '' into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/science/hdf5 DEBUG: OS darwin/10.8.0 (Mac OS X 10.6) arch i386 DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre- existing procedure. Target override will not be provided DEBUG: universal_variant is false, so not adding the default universal variant DEBUG: Not following dependencies Skipping deactivate hdf5 @1.6.9_1 (dry run) Skipping activate hdf5 @1.6.9_1 (dry run) DEBUG: Rebuilding port hdf5 finished with status 0 Warning: If this was no dry run, rev-upgrade would now run the checks again to find unresolved and newly created problems -- Ticket URL: <https://trac.macports.org/ticket/34494> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 11

[MacPorts] #35087: py27-gobject3 returned: configure failure: command execution failed
by MacPorts 05 Jul '12

05 Jul '12

#35087: py27-gobject3 returned: configure failure: command execution failed -------------------------------+-------------------------------------------- Reporter: dougalg@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Keywords: | Port: py27-gobject3 -------------------------------+-------------------------------------------- When attempting to install py27-gobject3 on OS X 10.7.4 py27-gobject3 failed to install because of: :info:configure configure: error: Package requirements (glib-2.0 >= 2.31.0 :info:configure gobject-introspection-1.0 >= 1.31.20 :info:configure ) were not met: :info:configure :info:configure No package 'gobject-introspection-1.0' found After installing that package it worked fine. Looks like it is just a missing dependency listing. -- Ticket URL: <https://trac.macports.org/ticket/35087> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #32611: Eterm crashes at launch
by MacPorts 05 Jul '12

05 Jul '12

#32611: Eterm crashes at launch ------------------------------------+--------------------------------------- Reporter: macleod@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: Eterm, lion | Port: Eterm ------------------------------------+--------------------------------------- Eterm will make but crashes and core dumps at launch: Eterm: Warning: Support for the utmp_logging attribute was not compiled in, ignoring Eterm: Warning: Support for the utmp_logging attribute was not compiled in, ignoring dyld: lazy symbol binding failed: Symbol not found: _blank_screen_mem Referenced from: /opt/local/lib/libEterm-0.9.5.dylib Expected in: flat namespace dyld: Symbol not found: _blank_screen_mem Referenced from: /opt/local/lib/libEterm-0.9.5.dylib Expected in: flat namespace Trace/BPT trap: 5 (core dumped) I have just migrated to Lion and recreated my MacPorts from scratch. THanks, Rob -- Ticket URL: <https://trac.macports.org/ticket/32611> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7