August 2013 - macports-tickets - lists.macosforge.org

[MacPorts] #20773: Add zope2.10
by MacPorts 14 Aug '14

14 Aug '14

#20773: Add zope2.10 -----------------------------+---------------------------------------------- Reporter: martin@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.7.1 Keywords: | Port: zope zope2.10 -----------------------------+---------------------------------------------- As stated on the mailing list ( http://lists.macosforge.org/pipermail /macports-users/2009-February/013697.html ) I think there should be a port for zope2.10 (and probably zope2.9, zope2.11). As with the different Python versions it is a dependency for other applications like Plone. The attached port file is tested with MacPorts 1.710, Mac OS X 10.5, Intel. -- Ticket URL: <http://trac.macports.org/ticket/20773> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #19397: scipy not completely universal
by MacPorts 14 Aug '14

14 Aug '14

#19397: scipy not completely universal -------------------------------------------+-------------------------------- Reporter: daweonline@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.1 Keywords: scipy python universal binary | Port: py26-scipy -------------------------------------------+-------------------------------- I've added "i386 x86_64" as universal flags in macports.conf. I've built python2.6 enabling universal and I successfully run it in 64 bit mode. I've built p26-scipy +universal but: {{{ >>> import scipy.signal Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6 /site-packages/scipy/signal/__init__.py", line 9, in <module> from bsplines import * File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6 /site-packages/scipy/signal/bsplines.py", line 3, in <module> import scipy.special File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6 /site-packages/scipy/special/__init__.py", line 8, in <module> from basic import * File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6 /site-packages/scipy/special/basic.py", line 8, in <module> from _cephes import * ImportError: dlopen(/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6 /site-packages/scipy/special/_cephes.so, 2): no suitable image found. Did find: /opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6 /site-packages/scipy/special/_cephes.so: mach-o, but wrong architecture }}} and also: {{{ >>> import scipy.linalg Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6 /site-packages/scipy/linalg/__init__.py", line 8, in <module> from basic import * File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6 /site-packages/scipy/linalg/basic.py", line 17, in <module> from lapack import get_lapack_funcs File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6 /site-packages/scipy/linalg/lapack.py", line 17, in <module> from scipy.linalg import flapack ImportError: dlopen(/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6 /site-packages/scipy/linalg/flapack.so, 2): no suitable image found. Did find: /opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6 /site-packages/scipy/linalg/flapack.so: mach-o, but wrong architecture }}} I've checked and there are a lot of others object only built for i386. Changing the universal flags to x86_64 only doesn't work. It appears that the build chain of scipy understands "universal" as "i386 ppc" only. {{{ $ port version Version: 1.710 $ uname -a Darwin host032.2b11.ifom-ieo-campus.it 9.6.3 Darwin Kernel Version 9.6.3: Tue Jan 20 18:26:40 PST 2009; root:xnu-1228.10.33~1/RELEASE_I386 i386 }}} -- Ticket URL: <http://trac.macports.org/ticket/19397> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 36

[MacPorts] #38091: alpine @2.00_4: update to 2.10
by MacPorts 13 Aug '14

13 Aug '14

#38091: alpine @2.00_4: update to 2.10 ----------------------+---------------------- Reporter: larryv@… | Owner: larryv@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: alpine ----------------------+---------------------- [http://patches.freeiz.com/alpine/info/alpine.html Alpine 2.10] has been released. We should probably update the `alpine` port. -- Ticket URL: <https://trac.macports.org/ticket/38091> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #37066: p5-shell-parser won't build
by MacPorts 13 Aug '14

13 Aug '14

#37066: p5-shell-parser won't build -----------------------------------------+-------------------------------- Reporter: ag@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: p5-shell-parser won't build | Port: p5-shell-parser -----------------------------------------+-------------------------------- Last lines of build: :debug:extract chowned /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5 -shell-parser/p5.12-shell-parser/work to macports :debug:extract euid/egid changed to: 503/501 :debug:extract Privilege de-escalation not attempted as not running as root. :debug:patch patch phase started at Tue Nov 20 20:43:34 CET 2012 :debug:patch Executing org.macports.patch (p5.12-shell-parser) :debug:patch Privilege de-escalation not attempted as not running as root. :debug:configure configure phase started at Tue Nov 20 20:43:34 CET 2012 :notice:configure ---> Configuring p5.12-shell-parser :debug:configure Using compiler 'Mac OS X clang' :debug:configure Executing org.macports.configure (p5.12-shell-parser) :debug:configure Environment: CPATH='/opt/local/include' CFLAGS='-pipe -O2' CPPFLAGS='-I/opt/local/include' CXXFLAGS='-pipe -O2' LIBRARY_PATH='/opt/local/lib' MACOSX_DEPLOYMENT_TARGET='10.8' CXX='/usr/bin/clang++' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5 -shell-parser/p5.12-shell-parser/work/.CC_PRINT_OPTIONS' F90FLAGS='-pipe -O2' LDFLAGS='-L/opt/local/lib' FCFLAGS='-pipe -O2' OBJC='/usr/bin/clang' INSTALL='/usr/bin/install -c' PERL_AUTOINSTALL='--skipdeps' OBJCFLAGS='-pipe -O2' FFLAGS='-pipe -O2' CC_PRINT_OPTIONS='YES' CC='/usr/bin/clang' :debug:configure Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5 -shell-parser/p5.12-shell-parser/work/Shell-Parser-0.04" && /opt/local/bin/perl5.12 Makefile.PL INSTALLDIRS=vendor CC="/usr/bin/clang" LD="/usr/bin/clang"' :debug:configure Executing command line: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5 -shell-parser/p5.12-shell-parser/work/Shell-Parser-0.04" && /opt/local/bin/perl5.12 Makefile.PL INSTALLDIRS=vendor CC="/usr/bin/clang" LD="/usr/bin/clang" :info:configure Checking if your kit is complete... :info:configure Looks good :info:configure Writing Makefile for Shell::Parser :debug:configure Executing proc-post-org.macports.configure-configure-0 :info:configure sed: RE error: illegal byte sequence :info:configure Command failed: find /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5 -shell-parser/p5.12-shell-parser/work/Shell-Parser-0.04 -name Makefile -type f -print0 | xargs -0 /usr/bin/sed -i "" '/^CCFLAGS *=/s/$/ /' ; :info:configure Exit code: 1 :error:configure org.macports.configure for port p5.12-shell-parser returned: command execution failed :debug:configure Error code: NONE :debug:configure Backtrace: command execution failed while executing "$post $targetname" :info:configure Warning: targets not executed for p5.12-shell-parser: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install :error:configure Failed to install p5.12-shell-parser :debug:configure Registry error: p5.12-shell-parser not registered as installed & active. invoked from within "registry_active ${subport}" invoked from within "$workername eval registry_active \${subport}" -- Ticket URL: <https://trac.macports.org/ticket/37066> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #36054: Feature request: reload action
by MacPorts 13 Aug '14

13 Aug '14

#36054: Feature request: reload action ----------------------------------+----------------------------------------- Reporter: mailtoarlo@… | Owner: macports-tickets@… Type: request | Status: new Priority: Low | Milestone: Component: base | Version: Keywords: | Port: ----------------------------------+----------------------------------------- When using ports that are started using launchd (e.g. apache2, mysql, php- fpm) the combination of {{{port unload}}} and {{{port load}}} is used to test configuration changes. Sadly typing this is long and cumbersome: {{{ sudo port unload apache2 && sudo port load apache2 }}} I suggest the {{{port reload}}} action that reduces the above to: {{{ sudo port reload apache2 }}} This is a common practice of "similar" commands like [http://manpages.ubuntu.com/manpages/hardy/en/man1/service.1.html service]. -- Ticket URL: <https://trac.macports.org/ticket/36054> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 13

[MacPorts] #37921: RFE: binutils's "notes" entry should specify which ports exactly it causes to fail to build
by MacPorts 13 Aug '14

13 Aug '14

#37921: RFE: binutils's "notes" entry should specify which ports exactly it causes to fail to build -------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: binutils -------------------------+-------------------------------- Right now binutils comes with the following "notes" entry in its portfile: {{{ "Having ${name} installed will cause some other ports to\ fail to build. Consider uninstalling ${name}." }}} I'd like to know which ports exactly these are, or at least have a link to a Trac ticket or something, so I can be better informed about whether I should actually follow this advice to uninstall it or not. -- Ticket URL: <https://trac.macports.org/ticket/37921> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #39065: Unable to upgrade Atlas on Snow Leopard 10.6.8
by MacPorts 13 Aug '14

13 Aug '14

#39065: Unable to upgrade Atlas on Snow Leopard 10.6.8 -------------------------+-------------------------------- Reporter: atif.azad@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: -------------------------+-------------------------------- Since I am behind a proxy, I ran the following commands (I am running OS X 10.6.8, and Xcode 3.2.6, macport 2.1.3: sudo port -d sync sudo port upgrade outdated ---> Computing dependencies for atlas ---> Building atlas Error: org.macports.build for port atlas returned: command execution failed Please see the log file for port atlas for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_math_atlas/atlas/main.log Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets -- Ticket URL: <https://trac.macports.org/ticket/39065> MacPorts <http://www.macports.org/> Ports system for OS X

1 39

[MacPorts] #32077: enforce-variants gtk2 +universal - @MacPorts version 2.03 - error
by MacPorts 13 Aug '14

13 Aug '14

#32077: enforce-variants gtk2 +universal - @MacPorts version 2.03 - error --------------------------------------------------------------------------------------------------------------------------------+ Reporter: adam.clay@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.0.3 Keywords: Scala, sudo port upgrade --enforce-variants gtk2 +universal , sudo port install fontconfig, sudo port install gtk2 | Port: fontconfig, gtk2, (enforce-variants gtk2 +universal) --------------------------------------------------------------------------------------------------------------------------------+ I am trying to install a free program called Scala that requires installation of MacPorts, and the ports "fontconfig" and "gtk2". These two seemed to install correctly from the terminal with the following commands: sudo port install fontconfig sudo port install gtk2 which tells me (if I understand the way MacPorts works) I installed both Macports, and these specific ports correctly. The instructions then ask me to modify my ".profile" file adding this line: export PATH=/opt/local/bin:/opt/local/sbin:$PATH which I did, and then install the libpng 1.4.5 or Combo Installer, which I did. Then, because I have a 64 bit Imac, I was asked to use the following terminal command: sudo port upgrade --enforce-variants gtk2 +universal, and when doing this I got the following error messsage: Error: Target org.macports.build returned: shell command failed (see log for details) Log for p5.12-xml-parser is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5 -xml-parser/p5.12-xml-parser/main.log Error: Unable to upgrade port: 1 Could anyone help me figure out why I cannot do this? -- Ticket URL: <https://trac.macports.org/ticket/32077> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 10

[MacPorts] #39300: libpqxx26 conflicts with libpqxx
by MacPorts 12 Aug '14

12 Aug '14

#39300: libpqxx26 conflicts with libpqxx --------------------------+-------------------------------- Reporter: ryandesign@… | Owner: dweber@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: libpqxx26, libpqxx --------------------------+-------------------------------- See summary: {{{ $ sudo port install compiler.blacklist=clang ---> Computing dependencies for libpqxx26 ---> Fetching distfiles for libpqxx26 ---> Verifying checksum(s) for libpqxx26 ---> Extracting libpqxx26 ---> Configuring libpqxx26 ---> Building libpqxx26 ---> Staging libpqxx26 into destroot ---> Installing libpqxx26 @2.6.9_0 ---> Activating libpqxx26 @2.6.9_0 Error: org.macports.activate for port libpqxx26 returned: Image error: /opt/local/bin/pqxx-config is being used by the active libpqxx port. Please deactivate this port first, or use 'port -f activate libpqxx26' to force the activation. Please see the log file for port libpqxx26 for details: /opt/local/var/macports/logs/_Users_rschmidt_macports_dports_databases_libpqxx26/libpqxx26/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port libpqxx26 failed }}} The ports either should not conflict, or should indicate that they do. -- Ticket URL: <https://trac.macports.org/ticket/39300> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #39299: libpqxx26 build fails with clang due to -Werror
by MacPorts 12 Aug '14

12 Aug '14

#39299: libpqxx26 build fails with clang due to -Werror --------------------------+----------------------- Reporter: ryandesign@… | Owner: dweber@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: libpqxx26 --------------------------+----------------------- Building libpqxx26 fails with clang because the configure script uses `-Werror` and also something that clang doesn't recommend. {{{ checking ability to compile programs using the standard C library... configure: error: Could not build even a tiny test program using the standard C library. Something very basic has gone wrong; try reading config.log to find out what. You'll probably want to go straight to the end of that file and read backwards until you find an error message. Then identify the problem, try to fix it, and run this script again. The configure script's --help option may provide useful tips on how to influence what compiler and command line options are used, what additional libraries are linked in, and so on. }}} config.log says: {{{ configure:20712: checking ability to compile programs using the standard C library configure:20737: /usr/bin/clang++ -c -pipe -Os -arch x86_64 -Werror -I/opt/local/include conftest.cpp >&5 conftest.cpp:32:18: error: using directive refers to implicitly-defined namespace 'std' [-Werror] using namespace std; ^ 1 error generated. }}} I guess the best fix is to remove `-Werror` in those places. -- Ticket URL: <https://trac.macports.org/ticket/39299> MacPorts <http://www.macports.org/> Ports system for OS X

1 1