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

[MacPorts] #41549: python34 installs fails with Image error: /opt/local/bin/2to3 already exists
by MacPorts 26 Nov '13

26 Nov '13

#41549: python34 installs fails with Image error: /opt/local/bin/2to3 already exists --------------------+-------------------------------- Reporter: nad@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: | Port: python34 --------------------+-------------------------------- As of Python 3.4.0b1, the Makefile `altintstall` and `install` targets have changed somewhat. In particular, for framework builds, there is now a complete set of symlinks created in the prefix bin directory ( {{{/opt/local/bin}}} for all of the files created in the framework `bin` directory. See http://bugs.python.org/issue19649 for details. `make install` will create files that overlap between Python versions, for example, the generic `python3` symlink. Another case is `2to3` which, I believe, exists in all Pythons since 2.6. The "already exists" error occurs when installing `python34` if `python27` is already installed. (I'm using a non-standard MacPorts prefix, `/macports`, instead of `/opt/local`, and use the `+universal` variant.) {{{ :error:activate org.macports.activate for port python34 returned: Image error: /macports/bin/2to3 already exists and does not belong to a registered port. Unable to activate port python34. Use 'port -f activate python34' to force the activation. }}} Here is the set of files to be installed by the `python34` port into the `bin` directory: {{{ :info:activate x ./macports/bin/2to3 :info:activate x ./macports/bin/2to3-3.4 :info:activate x ./macports/bin/easy_install-3.4 :info:activate x ./macports/bin/idle3 :info:activate x ./macports/bin/idle3.4 :info:activate x ./macports/bin/pip3 :info:activate x ./macports/bin/pip3.4 :info:activate x ./macports/bin/pydoc3 :info:activate x ./macports/bin/pydoc3.4 :info:activate x ./macports/bin/python3 :info:activate x ./macports/bin/python3-32 :info:activate x ./macports/bin/python3-config :info:activate x ./macports/bin/python3.4 :info:activate x ./macports/bin/python3.4-32 :info:activate x ./macports/bin/python3.4-config :info:activate x ./macports/bin/python3.4m :info:activate x ./macports/bin/python3.4m-config :info:activate x ./macports/bin/pyvenv :info:activate x ./macports/bin/pyvenv-3.4 }}} I currently have `python27` and `python33` installed. Here is what the `/macports/bin` directory looks like: {{{ # ls -l /macports/bin/pytho* lrwxr-xr-x 1 root admin 23 Nov 25 21:06 /macports/bin/python@ -> /macports/bin/python2.7 lrwxr-xr-x 1 root admin 30 Nov 25 21:06 /macports/bin/python-config@ -> /macports/bin/python2.7-config lrwxr-xr-x 1 root admin 72 Nov 12 13:58 /macports/bin/python2.7@ -> /macports/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 lrwxr-xr-x 1 root admin 79 Nov 12 13:58 /macports/bin/python2.7-config@ -> /macports/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7-config lrwxr-xr-x 1 root admin 23 Aug 23 13:45 /macports/bin/python3@ -> /macports/bin/python3.3 lrwxr-xr-x 1 root admin 72 Nov 25 20:49 /macports/bin/python3.3@ -> /macports/Library/Frameworks/Python.framework/Versions/3.3/bin/python3.3 lrwxr-xr-x 1 root admin 75 Nov 25 20:49 /macports/bin/python3.3-32@ -> /macports/Library/Frameworks/Python.framework/Versions/3.3/bin/python3.3-32 lrwxr-xr-x 1 root admin 79 Nov 25 20:49 /macports/bin/python3.3-config@ -> /macports/Library/Frameworks/Python.framework/Versions/3.3/bin/python3.3-config lrwxr-xr-x 1 root admin 24 Nov 25 21:06 /macports/bin/pythonw@ -> /macports/bin/pythonw2.7 lrwxr-xr-x 1 root admin 73 Nov 12 13:58 /macports/bin/pythonw2.7@ -> /macports/Library/Frameworks/Python.framework/Versions/2.7/bin/pythonw2.7 lrwxr-xr-x 1 root admin 73 Nov 25 20:49 /macports/bin/pythonw3.3@ -> /macports/Library/Frameworks/Python.framework/Versions/3.3/bin/pythonw3.3 lrwxr-xr-x 1 root admin 76 Nov 25 20:49 /macports/bin/pythonw3.3-32@ -> /macports/Library/Frameworks/Python.framework/Versions/3.3/bin/pythonw3.3-32 # ls -l /macports/bin/2to* lrwxr-xr-x 1 root admin 22 Nov 25 21:06 /macports/bin/2to3@ -> /macports/bin/2to3-2.7 lrwxr-xr-x 1 root admin 71 Nov 12 13:58 /macports/bin/2to3-2.7@ -> /macports/Library/Frameworks/Python.framework/Versions/2.7/bin/2to3-2.7 lrwxr-xr-x 1 root admin 71 Nov 25 20:49 /macports/bin/2to3-3.3@ -> /macports/Library/Frameworks/Python.framework/Versions/3.3/bin/2to3-3.3 }}} Along with the `2to3` conflict, there will likely be conflicts between the `python33` and `python34` versions of the `3` links. Without thinking too much about it, I think the right approach would likely be to install with `make altinstall` rather then `make install` and then provide `port select python3` options and just special case `2to3`, perhaps giving preference to the Python 3.x version which should be newer. Also, note that Python 3.4.0b1 implements PEP 453 which by default installs a version of `pip` and its current dependency `setuptools`, which now show up in the bin directories and will conflict with the `py34-setuptools` port and `py34-pip` (when created). See http://bugs.python.org/issue19553 for more details. -- Ticket URL: <https://trac.macports.org/ticket/41549> MacPorts <http://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #40330: hugin-app: failure to compile when including boost headers
by MacPorts 26 Nov '13

26 Nov '13

#40330: hugin-app: failure to compile when including boost headers ---------------------+-------------------------------- Reporter: mojca@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: hugin-app boost ---------------------+-------------------------------- hugin-app (both 2012.0.0 and the latest version from RCS at the time of writing) fails to compile with boost @1.54.0, at least on Lion. The list of errors is long, but here's the first one, most likely related to a weird mixture of Apple and boost headers conflicting with each other: {{{ In file included from /work/hugin-2012.0.0/src/hugin_base/huginapp/ImageCache.h:30: In file included from /opt/local/include/boost/signal.hpp:27: In file included from /opt/local/include/boost/signals/signal0.hpp:24: In file included from /opt/local/include/boost/signals/signal_template.hpp:21: In file included from /opt/local/include/boost/signals/slot.hpp:15: In file included from /opt/local/include/boost/signals/trackable.hpp:13: In file included from /opt/local/include/boost/type_traits.hpp:35: In file included from /opt/local/include/boost/type_traits/has_operator.hpp:12: In file included from /opt/local/include/boost/type_traits/has_bit_and.hpp:43: /opt/local/include/boost/type_traits/detail/has_binary_operator.hpp:157:121: error: expected expression BOOST_STATIC_CONSTANT(bool, value = (sizeof(check(((make<Lhs>() BOOST_TT_TRAIT_OP make<Rhs>()),make<has_operator>())))==sizeof(::boost::type_traits::yes_type))); ^ /opt/local/include/boost/config/suffix.hpp:393:72: note: expanded from macro 'BOOST_STATIC_CONSTANT' # define BOOST_STATIC_CONSTANT(type, assignment) static const type assignment ^ }}} -- Ticket URL: <https://trac.macports.org/ticket/40330> MacPorts <http://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #40593: wesnoth: port abandoned
by MacPorts 26 Nov '13

26 Nov '13

#40593: wesnoth: port abandoned --------------------------+---------------------- Reporter: ryandesign@… | Owner: jordan@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: wesnoth --------------------------+---------------------- The maintainer has not responded to the last several port update tickets: * #40526 - 1.10.7 * #38812 - 1.10.6 * #37447 - 1.10.5 * #35935 - 1.10.4 * #33655 - 1.10.3 * #30843 - 1.8.6 * #26741 - 1.8.5 In fact I don't think there has been any involvement from the maintainer since he requested to be the maintainer in #25240 and provided an update to 1.8.2. Jordan, do you still exist, and still wish to be listed as this port's maintainer? If I don't hear from you by November 1, 2013, I'll remove you as this port's maintainer. -- Ticket URL: <https://trac.macports.org/ticket/40593> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #41551: Terminal does not find vte
by MacPorts 26 Nov '13

26 Nov '13

#41551: Terminal does not find vte -----------------------+-------------------------------- Reporter: rudloff@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: | Port: Terminal -----------------------+-------------------------------- Terminal does not seem to find vte: {{{ checking for vte >= 0.17.1... not found *** The required package vte was not found on your system. *** Please install vte (atleast version 0.17.1) or adjust *** the PKG_CONFIG_PATH environment variable if you *** installed the package in a nonstandard prefix so that *** pkg-config is able to find it. }}} But I do have this port installed: {{{ ws-Jose-iMac20:~ prudloff$ port install vte ---> Computing dependencies for vte ---> Cleaning vte ---> Scanning binaries for linking errors: 100.0% ---> No broken files found }}} -- Ticket URL: <https://trac.macports.org/ticket/41551> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #41463: hugin-app @2013.0.0 fails: "recursive template instantiation exceeded maximum depth"
by MacPorts 26 Nov '13

26 Nov '13

#41463: hugin-app @2013.0.0 fails: "recursive template instantiation exceeded maximum depth" --------------------------+-------------------------------- Reporter: gunnlaugur@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: | Port: hugin-app --------------------------+-------------------------------- Building hugin-app @2013.0.0 fails with this: {{{ :info:build /opt/local/include/boost/fusion/view/transform_view/detail/value_of_impl.hpp:32:32: fatal error: recursive template instantiation exceeded maximum depth of 128 :info:build result_of::value_of<typename Iterator::first_type>::type :info:build ^ }}} followed by a stack of template instantiation contexts, see attached `main.log`. -- Ticket URL: <https://trac.macports.org/ticket/41463> MacPorts <http://www.macports.org/> Ports system for OS X

1 9

[MacPorts] #40628: enblend @4.0: update to 4.1.1
by MacPorts 26 Nov '13

26 Nov '13

#40628: enblend @4.0: update to 4.1.1 ---------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: enblend ---------------------+-------------------------------- {{{ Local-Admins-MacBook-Pro:~ root# port -v livecheck enblend enblend seems to have been updated (port version: 4.0, new version: 4.1.1) }}} I tried doing the update myself but I couldn't figure out how to write the new `master_sites`... -- Ticket URL: <https://trac.macports.org/ticket/40628> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #28021: enblend uses gnuplot without declaring dependency
by MacPorts 26 Nov '13

26 Nov '13

#28021: enblend uses gnuplot without declaring dependency -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: hvdwolf@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: enblend -------------------------------------+-------------------------------------- The enblend build process uses gnuplot, but the enblend port does not declare a dependency on the gnuplot port. -- Ticket URL: <https://trac.macports.org/ticket/28021> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #40761: py-psycopg2 @2.4.6: Update to 2.5.1
by MacPorts 26 Nov '13

26 Nov '13

#40761: py-psycopg2 @2.4.6: Update to 2.5.1 -----------------------------+-------------------------------- Reporter: md14-macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: haspatch | Port: py-psycopg2 -----------------------------+-------------------------------- The attached patch updates py-psycopg2 to 2.5.1 and fixes a nonworking homepage URL. Thanks! -- Ticket URL: <https://trac.macports.org/ticket/40761> MacPorts <http://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #41531: avahi upgrade fails - can't find pygtk
by MacPorts 25 Nov '13

25 Nov '13

#41531: avahi upgrade fails - can't find pygtk ------------------------------+-------------------------------- Reporter: david.w.watson@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: | Port: avahi ------------------------------+-------------------------------- See log. -- Ticket URL: <https://trac.macports.org/ticket/41531> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #41495: neon: missing dependency on kerberos5
by MacPorts 25 Nov '13

25 Nov '13

#41495: neon: missing dependency on kerberos5 ----------------------+--------------------- Reporter: devans@… | Owner: dluke@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: | Port: neon ----------------------+--------------------- if kerberos5 is installed libneon links with the following libraries for optional gssapi support. {{{ libgssapi_krb5.2.2.dylib libkrb5.3.3.dylib libk5crypto.3.1.dylib }}} but kerberos5 is not in its dependency tree and gssapi support is enabled by default Probably need to add this dependency or disable gssapi support to ensure a consistent build -- Ticket URL: <https://trac.macports.org/ticket/41495> MacPorts <http://www.macports.org/> Ports system for OS X

1 4