April 2009 - macports-tickets - lists.macosforge.org

[MacPorts] #19013: Xfig does not start with "Error:
by MacPorts 07 Aug '10

07 Aug '10

#19013: Xfig does not start with "Error: --------------------------------+------------------------------------------- Reporter: younghan@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: xfig | Port: xfig --------------------------------+------------------------------------------- Fresh install of xfig 3.2.5_5 (on Macports 1.700 on OSX 10.5.6, native X11) crashes with "Error" Unresolved inheritance operation". Could be related to Ticket #18815, but the patches there must have been already incorporated in release 5. (Perhaps it's the bug introduced by release 5.) $X -version Xquartz starting: X.org Release 7.2 X.Org X Server 1.3.0-apple22 Build Date: 20080821 $otool -L /opt/local/bin/xfig /opt/local/bin/xfig: /opt/local/lib/libjpeg.62.dylib (compatibility version 63.0.0, current version 63.0.0) /opt/local/lib/libXpm.4.dylib (compatibility version 16.0.0, current version 16.0.0) /opt/local/lib/libpng12.0.dylib (compatibility version 36.0.0, current version 36.0.0) /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3) /usr/X11/lib/libXi.6.dylib (compatibility version 7.0.0, current version 7.0.0) /opt/local/lib/libXaw3d.8.dylib (compatibility version 8.0.0, current version 8.0.0) /opt/local/lib/libXmu.6.dylib (compatibility version 9.0.0, current version 9.0.0) /opt/local/lib/libXt.6.dylib (compatibility version 7.0.0, current version 7.0.0) /opt/local/lib/libSM.6.dylib (compatibility version 7.0.0, current version 7.0.0) /opt/local/lib/libICE.6.dylib (compatibility version 10.0.0, current version 10.0.0) /opt/local/lib/libXp.6.dylib (compatibility version 9.0.0, current version 9.0.0) /opt/local/lib/libXext.6.dylib (compatibility version 11.0.0, current version 11.0.0) /opt/local/lib/libX11.6.dylib (compatibility version 9.0.0, current version 9.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.3) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) -- Ticket URL: <http://trac.macports.org/ticket/19013> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #16334: RFE: Make Python more Framework Friendly
by MacPorts 06 Aug '10

06 Aug '10

#16334: RFE: Make Python more Framework Friendly -----------------------------------+---------------------------------------- Reporter: mcalhoun(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Keywords: | -----------------------------------+---------------------------------------- To ease the transition when python25 enabled the Framework option (in r37817), it was decided to move the actual library and include directories to ${prefix}/lib and ${prefix}/include respectively. {{{ foreach dir { lib include } { file rename ${destroot}${framewdir}/${dir}/python${branch} ${destroot}${prefix}/${dir} ln -s ${prefix}/${dir}/python${branch} ${destroot}${framewdir}/${dir}/python${branch} } }}} This can cause a problem because some scripts ask python directly where the library directory is. Python believes that the library directory is on the Framework directory. There is a discussion on the mailing list [http://lists.macosforge.org/pipermail/macports-dev/2008-July/005603.html on this problem]. We can put the effort into making ports work with the current python setup, but I humbly suggest that a better long term solution is to to modify the various ports to install into the Framework directory. Attached is a proposed change to the python25 Portfile as well as the python25 group. The advantages are: * The python program will not have the wrong library path. * It is much easier to avoid conflicts between the versions of python. The main disadvantage is that many ports will have to be modified (only minor changes, however, are often sufficient). Of the py25-* ports I have tested, the most common changes required are along the lines of: {{{ configure.pre_args-delete --prefix=${prefix} set python_prefix ${prefix}/Library/Frameworks/Python.framework/Versions/2.5 configure.pre_args-append --prefix=${python_prefix} configure.args-append --includedir=${python_prefix}/include/python2.5 configure.env-append PKG_CONFIG_PATH=${python_prefix}/lib/pkgconfig }}} -- Ticket URL: <http://trac.macports.org/ticket/16334> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 13

[MacPorts] #19473: AACGain 1.8
by MacPorts 04 Aug '10

04 Aug '10

#19473: AACGain 1.8 -------------------------------------+-------------------------------------- Reporter: tjb@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Port Binaries Component: ports | Version: 1.7.1 Keywords: | Port: -------------------------------------+-------------------------------------- AACGain 1.8 is out. I'm only just starting to use it so I'm not sure if there's a good reason not to upgrade. -- Ticket URL: <http://trac.macports.org/ticket/19473> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #18294: pure-0.16: broken man page
by MacPorts 03 Aug '10

03 Aug '10

#18294: pure-0.16: broken man page -------------------------------+-------------------------------------------- Reporter: godboutn@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: | Port: pure -------------------------------+-------------------------------------------- {{{ man pure }}} reports no documentation after installation of pure-0.16. The problem is due to an invalid soft link {{{ pure.1@ -> pure-0.16.1 }}} whereas the man page itself is compressed and has the name {{{pure-0.16.1.gz}}}. A patch file fixing the problem in the post-destroot phase is included below. -- Ticket URL: <http://trac.macports.org/ticket/18294> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #16511: zeroinstall-injector fails with pygtk problem
by MacPorts 30 Jul '10

30 Jul '10

#16511: zeroinstall-injector fails with pygtk problem ------------------------------+--------------------------------------------- Reporter: wsc9tt(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: pygtk | Port: zeroinstall-injector ------------------------------+--------------------------------------------- The zeroinstall-injector package builds and installs fine but here is a sample from running it: mbp ~ $ 0launch --gui Traceback (most recent call last): File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5 /site-packages/zeroinstall/0launch-gui/0launch-gui", line 11, in <module> import pygtk; pygtk.require('2.0') ImportError: No module named pygtk It appears to be missing some dependency. This is from a fresh install of macports on a Leopard machine. -- Ticket URL: <http://trac.macports.org/ticket/16511> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 13

[MacPorts] #19122: OpenSSL 1.0.0-beta1 breaks packages that expect libcrypto.0.9.8
by MacPorts 30 Jul '10

30 Jul '10

#19122: OpenSSL 1.0.0-beta1 breaks packages that expect libcrypto.0.9.8 -----------------------------------------------+---------------------------- Reporter: bretthoerner@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: git openssl libcrypto 1.0.0 0.9.8 | Port: openssl -----------------------------------------------+---------------------------- 1.0.0 apparently replaces 0.9.8 rather than installing alongside it, {{ $ git svn fetch dyld: Library not loaded: /opt/local/lib/libcrypto.0.9.8.dylib Referenced from: /opt/local/bin/git Reason: image not found Trace/BPT trap }} Is this expected? Should I be rebuilding all packages that depend on OpenSSL? -- Ticket URL: <http://trac.macports.org/ticket/19122> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 15

[MacPorts] #18483: perlmagic no longer compiles
by MacPorts 27 Jul '10

27 Jul '10

#18483: perlmagic no longer compiles -------------------------------------+-------------------------------------- Reporter: matt.hilliard@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: | Port: perlmagic -------------------------------------+-------------------------------------- calling: $ sudo port install p5-perlmagick runs through installing ImageMagic, and perl and python, and X libraries and the kitchen sink but it won't install perlmagick The relevant console bits are attached. -- Ticket URL: <http://trac.macports.org/ticket/18483> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #18878: mod_python 3.3.1_1 "Target org.macports.activate returned: Not a directory"
by MacPorts 27 Jul '10

27 Jul '10

#18878: mod_python 3.3.1_1 "Target org.macports.activate returned: Not a directory" -------------------------------+-------------------------------------------- Reporter: francis@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: | Port: mod_python -------------------------------+-------------------------------------------- When I try to install mod_python I get the following error: {{{ ---> Fetching mod_python ---> Verifying checksum(s) for mod_python ---> Extracting mod_python ---> Applying patches to mod_python ---> Configuring mod_python ---> Building mod_python ---> Staging mod_python into destroot Warning: mod_python requests to install files outside the common directory structure! ---> Installing mod_python @3.3.1_1 ######################################################## # to enable mod_python add # LoadModule python_module modules/mod_python.so # to your apache2 config file: # /opt/local/apache2/conf/httpd.conf ######################################################## ---> Activating mod_python @3.3.1_1 Error: Target org.macports.activate returned: Not a directory Error: Status 1 encountered during processing. }}} After the error, some of the files (e.g. /opt/local/apache2/modules/mod_python.so) seem to have been created, but mod_python does not work - after adding "LoadModule python_module modules/mod_python.so" to http.conf and restarting apache2 I see the following error repeated in /opt/local/apache2/logs/error_log: {{{ Tue Mar 17 12:39:32 2009] [notice] child pid 2288 exit signal Bus error (10) [Tue Mar 17 12:39:32 2009] [notice] child pid 2287 exit signal Bus error (10) [Tue Mar 17 12:39:34 2009] [notice] child pid 2286 exit signal Bus error (10) [Tue Mar 17 12:39:34 2009] [notice] child pid 2285 exit signal Bus error (10) [Tue Mar 17 12:39:34 2009] [notice] child pid 2284 exit signal Bus error (10) [Tue Mar 17 12:39:34 2009] [notice] child pid 2283 exit signal Bus error (10) [Tue Mar 17 12:39:34 2009] [notice] child pid 2282 exit signal Bus error (10) }}} -- Ticket URL: <http://trac.macports.org/ticket/18878> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #18804: p5-mail-spamassassin 3.2.5_2: spamd cannot see the user's auto-whitelist file
by MacPorts 26 Jul '10

26 Jul '10

#18804: p5-mail-spamassassin 3.2.5_2: spamd cannot see the user's auto-whitelist file ---------------------------------+------------------------------------------ Reporter: vinc17@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: | Port: p5-mail-spamassassin ---------------------------------+------------------------------------------ I use SpamAssassin via spamc and spamd, and in my log messages (/var/log/mail.log), I get messages like: {{{ Mar 12 12:45:52 prunille spamd[25703]: spamd: connection from localhost [127.0.0.1] at port 64347 Mar 12 12:45:52 prunille spamd[25703]: spamd: setuid to vinc17 succeeded Mar 12 12:45:53 prunille spamd[25703]: spamd: processing message <20090312113155.GK16527(a)prunille.vinc17.org> for vinc17:501 Mar 12 12:45:57 prunille spamd[25703]: auto-whitelist: open of auto- whitelist file failed: auto-whitelist: cannot open auto_whitelist_path /Users/vinc17/.spamassassin/auto-whitelist: No such file or directory Mar 12 12:45:58 prunille spamd[25703]: spamd: clean message (0.0/5.0) for vinc17:501 in 5.6 seconds, 2626 bytes. Mar 12 12:45:58 prunille spamd[25703]: spamd: result: . 0 - scantime=5.6,size=2626,user=vinc17,uid=501,required_score=5.0,rhost=localhost,raddr=127.0.0.1,rport=64347,mid=<20090312113155.GK16527(a)prunille.vinc17.org>,autolearn=ham Mar 12 12:45:58 prunille spamd[25699]: prefork: child states: II }}} However /Users/vinc17/.spamassassin/auto-whitelist really exists: {{{ $ ls -l /Users/vinc17/.spamassassin/auto-whitelist -rw------- 1 vinc17 vinc17 5255168 2009-03-12 00:32:11 /Users/vinc17/.spamassassin/auto-whitelist }}} -- Ticket URL: <http://trac.macports.org/ticket/18804> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #16912: qtpfsgui won't run
by MacPorts 25 Jul '10

25 Jul '10

#16912: qtpfsgui won't run --------------------------------+------------------------------------------- Reporter: dersh(a)alum.mit.edu | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: qtpfsgui exiv | Port: qtpfsgui --------------------------------+------------------------------------------- When I try to double click on qtpfsgui I get a error of: Library not loaded: /opt/local/lib/libexiv2.0.dylib Referenced from: /Applications/MacPorts/qtpfsgui.app/Contents/MacOS/qtpfsgui I checked and in fact that library doesn't exist. I see that exiv2 provides: /opt/local/lib/libexiv2.dylib /opt/local/lib/libexiv2.4.dylib /opt/local/lib/libexiv2.4.0.1.dylib My guess is that a recent upgrade of exiv2 broke the link. I tried this as a work around: {{{ sudo ln -s /opt/local/lib/libexiv2.4.0.1.dylib /opt/local/lib/libexiv2.0.dylib }}} and now it does open. I am not sure if exiv2 really should have that link, or if qtpfsgui really should be looking for libexiv2.dylib rather then libexif2.0. But the current combination doesn't work. -- Ticket URL: <http://trac.macports.org/ticket/16912> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7