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

[MacPorts] #49500: fltk@1.3.3 build fails because header objc/NSObjCRuntime.h not found
by MacPorts 10 Nov '15

10 Nov '15

#49500: fltk(a)1.3.3 build fails because header objc/NSObjCRuntime.h not found -------------------------+-------------------------------- Reporter: nico.mack@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: fltk(a)1.3.3 -------------------------+-------------------------------- fltk version 1.3.3 fails to build against libc++ runtime on OSX10.8.5 with XCode 5.1.1 installed. Macports was previously cleaned {{{ sudo port clean --all all sudo port uninstall installed }}} fltk is being installed as a dependency for octave. Log of clean build attached. -- Ticket URL: <https://trac.macports.org/ticket/49500> MacPorts <https://www.macports.org/> Ports system for OS X

1 6

Re: [MacPorts] #41145: py26-pyobjc: track removal (was: py26-pyobjc needs to be downgraded to a Python 2.6-compatible version)
by MacPorts 10 Nov '15

10 Nov '15

#41145: py26-pyobjc: track removal ---------------------------+---------------------- Reporter: ryandesign@… | Owner: petr@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: py26-pyobjc | ---------------------------+---------------------- Description changed by petr@…: Old description: > https://bitbucket.org/ronaldoussoren/pyobjc/issue/58/python-26-is-not- > really-supported New description: [Summary was: py26-pyobjc needs to be downgraded to a Python 2.6-compatible version] https://bitbucket.org/ronaldoussoren/pyobjc/issue/58/python-26-is-not- really-supported -- -- Ticket URL: <https://trac.macports.org/ticket/41145#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #46429: nmap @6.47 +zenmap python modules not installed correctly
by MacPorts 10 Nov '15

10 Nov '15

#46429: nmap @6.47 +zenmap python modules not installed correctly -------------------------------+-------------------------------- Reporter: ulrich.felzmann@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: zenmap python | Port: nmap @6.47 +zenmap -------------------------------+-------------------------------- zenmap can't find its python modules since they are installed in lib/python2.7/site-packages/zenmap instead of Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site- packages I guess. {{{ zenmap Could not import the zenmapGUI.App module: 'No module named zenmapGUI.App'. I checked in these directories: /opt/macports/bin /opt/macports/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/py2app-0.9-py2.7.egg /opt/macports/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/modulegraph-0.12-py2.7.egg /opt/macports/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/altgraph-0.12-py2.7.egg /opt/macports/Library/Frameworks/Python.framework/Versions/2.7/lib/python27.zip /opt/macports/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /opt/macports/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /plat-darwin /opt/macports/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /plat-mac /opt/macports/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /plat-mac/lib-scriptpackages /opt/macports/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /lib-tk /opt/macports/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /lib-old /opt/macports/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/readline /opt/macports/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /lib-dynload /opt/macports/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages /opt/macports/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/gtk-2.0 /opt/macports/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/pyspread/src /opt/macports/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/wx-3.0-osx_cocoa If you installed Zenmap in another directory, you may have to add the modules directory to the PYTHONPATH environment variable. }}} Works by manually setting the PYTHONPATH to lib/python2.7/site- packages/zenmap. -- Ticket URL: <https://trac.macports.org/ticket/46429> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

Re: [MacPorts] #41145: py26-pyobjc needs to be downgraded to a Python 2.6-compatible version
by MacPorts 10 Nov '15

10 Nov '15

#41145: py26-pyobjc needs to be downgraded to a Python 2.6-compatible version ---------------------------+---------------------- Reporter: ryandesign@… | Owner: petr@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: py26-pyobjc | ---------------------------+---------------------- Comment (by petr@…): Adding maintainers of the relevant port. -- Ticket URL: <https://trac.macports.org/ticket/41145#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #41145: py26-pyobjc needs to be downgraded to a Python 2.6-compatible version
by MacPorts 10 Nov '15

10 Nov '15

#41145: py26-pyobjc needs to be downgraded to a Python 2.6-compatible version ---------------------------+---------------------- Reporter: ryandesign@… | Owner: petr@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: py26-pyobjc | ---------------------------+---------------------- Changes (by petr@…): * cc: aronnax@…, jjstickel@…, Tom.Schoonjans@…, chiszp@…, eborisch@…, robitaille@…, g5pw@…, stromnov@… (added) -- Ticket URL: <https://trac.macports.org/ticket/41145#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #49335: py-gmpy @1.17: Add py35 subport
by MacPorts 10 Nov '15

10 Nov '15

#49335: py-gmpy @1.17: Add py35 subport ---------------------------------+-------------------------------- Reporter: md14-macports@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: haspatch maintainer | Port: py-gmpy ---------------------------------+-------------------------------- The attached patch adds the py35-gmpy subport. -- Ticket URL: <https://trac.macports.org/ticket/49335> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #49645: `port -n upgrade --force foo` should deactivate after creating the new archive
by MacPorts 10 Nov '15

10 Nov '15

#49645: `port -n upgrade --force foo` should deactivate after creating the new archive -------------------------+-------------------------------- Reporter: rjvbertin@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Keywords: | Port: -------------------------+-------------------------------- I think this has only been touched up on the ML: Currently, reinstalling a port with `port -n upgrade --force foo` will u0) do an archivefetch or verify if the `port destroot` phase has been terminated u1) deactivate the currently active version of foo u2) create the archive in ${prefix}/var/macports/software/foo u3) activate that archive (unpack it, move files into place) Installing a new version of the same port has the following operation sequence: i0) do an archivefetch or verify if the `port destroot` phase has been terminated i1) create the archive in ${prefix}/var/macports/software/foo i2) deactivate the currently active version of foo i3) activate that archive (unpack it, move files into place) The sequence i1,i2 is appropriate, the sequence u1,u2 much less. The difference becomes noticeable when `foo` is a large port like Qt: the lapse of time that no version is active is significantly longer than required and desirable. Indeed, running dependents can run into issues; this is clearly then case with KDE PIM applications like kmail (and its myriad of helper agents) which tend to abort or crash when Qt disappears for long enough. NB: doing `port upgrade foo` of a port that has a new version pending has the same sequence order, i1,i2! I have had a look at macports::_upgrade but that procedure is too complex to assess easily whether the u1 and u2 can be interchanged in the upgrade sequence. However, I don't see the difference between reinstalling the same version of a port (via upgrade --force) or upgrading to a new version, so I assume that that same order of operations can be followed during a reinstall. Hence filing a '''defect''' ticket instead of an '''enhancement''' request. -- Ticket URL: <https://trac.macports.org/ticket/49645> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #49620: apbs fails to upgrade
by MacPorts 10 Nov '15

10 Nov '15

#49620: apbs fails to upgrade -----------------------+-------------------------------- Reporter: summers@… | Owner: macports-tickets@… Type: update | Status: new Priority: High | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: -----------------------+-------------------------------- Attempted to upgrade apbs; El Capitan 10.11.2 Beta (15C31f); MacBook Pro Late 2013 ---> Building apbs Error: org.macports.build for port apbs returned: command execution failed Please see the log file for port apbs for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_apbs/apbs/main.log Error: Unable to upgrade port: 1 -- Ticket URL: <https://trac.macports.org/ticket/49620> MacPorts <https://www.macports.org/> Ports system for OS X

1 6

[MacPorts] #49646: `port -n upgrade --force foo` should deactivate after creating the new archive
by MacPorts 10 Nov '15

10 Nov '15

#49646: `port -n upgrade --force foo` should deactivate after creating the new archive -------------------------+-------------------------------- Reporter: rjvbertin@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Keywords: | Port: -------------------------+-------------------------------- I think this has only been touched up on the ML: Currently, reinstalling a port with `port -n upgrade --force foo` will u0) do an archivefetch or verify if the `port destroot` phase has been terminated u1) deactivate the currently active version of foo u2) create the archive in ${prefix}/var/macports/software/foo u3) activate that archive (unpack it, move files into place) Installing a new version of the same port has the following operation sequence: i0) do an archivefetch or verify if the `port destroot` phase has been terminated i1) create the archive in ${prefix}/var/macports/software/foo i2) deactivate the currently active version of foo i3) activate that archive (unpack it, move files into place) The sequence i1,i2 is appropriate, the sequence u1,u2 much less. The difference becomes noticeable when `foo` is a large port like Qt: the lapse of time that no version is active is significantly longer than required and desirable. Indeed, running dependents can run into issues; this is clearly then case with KDE PIM applications like kmail (and its myriad of helper agents) which tend to abort or crash when Qt disappears for long enough. NB: doing `port upgrade foo` of a port that has a new version pending has the same sequence order, i1,i2! I have had a look at macports::_upgrade but that procedure is too complex to assess easily whether the u1 and u2 can be interchanged in the upgrade sequence. However, I don't see the difference between reinstalling the same version of a port (via upgrade --force) or upgrading to a new version, so I assume that that same order of operations can be followed during a reinstall. Hence filing a '''defect''' ticket instead of an '''enhancement''' request. -- Ticket URL: <https://trac.macports.org/ticket/49646> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #49375: unable to upgrade clang-3.4
by MacPorts 10 Nov '15

10 Nov '15

#49375: unable to upgrade clang-3.4 ------------------------------------+-------------------------------- Reporter: p.fabrizio.salvatore@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: ------------------------------------+-------------------------------- Hi, when running port upgrade outdated (after a selfupdate) I have the following error message: Error: org.macports.build for port clang-3.4 returned: command execution failed and the log of the error is attached to this email. Is this something known? Thanks! Fab -- Ticket URL: <https://trac.macports.org/ticket/49375> MacPorts <https://www.macports.org/> Ports system for OS X

1 4