[MacPorts] #48075: py27-pycparser @2.14_0: upgrade fails during destroot
#48075: py27-pycparser @2.14_0: upgrade fails during destroot ----------------------+-------------------------- Reporter: devans@… | Owner: stromnov@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: py-pycparser ----------------------+-------------------------- {{{ :info:destroot running install_scripts :info:destroot running build_scripts :info:destroot error: cannot copy tree 'build/scripts-2.7': not a directory :info:destroot Command failed: cd "/opt/local/var/macports/build /_opt_macports_trunk_dports_python_py- pycparser/py27-pycparser/work/pycparser-2.14" && /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 setup.py --no-user-cfg install --prefix=/opt/local/Library/Frameworks/Python.framework/Versions/2.7 --root=/opt/local/var/macports/build/_opt_macports_trunk_dports_python_py- pycparser/py27-pycparser/work/destroot }}} Full log attached -- Ticket URL: <https://trac.macports.org/ticket/48075> MacPorts <https://www.macports.org/> Ports system for OS X
#48075: py27-pycparser @2.14_0: upgrade fails during destroot ---------------------------+------------------------ Reporter: devans@… | Owner: stromnov@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: py-pycparser | ---------------------------+------------------------ Changes (by devans@…): * cc: larryv@… (added) Comment: Although the build seems to have succeeded on the buildbots, locally I'm seeing this same exact failure during destroot with py27-cryptography. Any suggestions on how to get around this would be appreciated. -- Ticket URL: <https://trac.macports.org/ticket/48075#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#48075: py27-pycparser @2.14_0: upgrade fails during destroot ---------------------------+------------------------ Reporter: devans@… | Owner: stromnov@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: invalid | Keywords: Port: py-pycparser | ---------------------------+------------------------ Changes (by devans@…): * status: new => closed * resolution: => invalid Comment: Closing as invalid. Apparently a configuration issue on one machine only. Removing and reinstalling MacPorts seems to have fixed the issue. -- Ticket URL: <https://trac.macports.org/ticket/48075#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts