#50244: port upgrade outdated is unable to upgrade py34-setuptools ----------------------------+------------------- Reporter: port@… | Owner: jmr@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: py-setuptools | ----------------------------+------------------- Old description:

$ port upgrade outdated ---> Computing dependencies for py34-setuptools ---> Building py34-setuptools Error: org.macports.build for port py34-setuptools returned: command execution failed

New description: {{{ $ port upgrade outdated ---> Computing dependencies for py34-setuptools ---> Building py34-setuptools Error: org.macports.build for port py34-setuptools returned: command execution failed }}} -- Comment (by mf2k@…): In the future, please use WikiFormatting. -- Ticket URL: <https://trac.macports.org/ticket/50244#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X

#50244: port upgrade outdated is unable to upgrade py34-setuptools ----------------------------+------------------- Reporter: port@… | Owner: jmr@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: py-setuptools | ----------------------------+------------------- Comment (by port@…): Apparently this is not an issue on py-* port or others but a misconfiguration known and reported in [https://trac.macports.org/ticket/49101 #49101] [[BR]] The solution described worked for me : {{{ % sudo mkdir -p /opt/local/var/macports/home % sudo chown macports:macports /opt/local/var/macports/home }}} -- Ticket URL: <https://trac.macports.org/ticket/50244#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X

#50244: port upgrade outdated is unable to upgrade py34-setuptools ----------------------------+------------------- Reporter: port@… | Owner: jmr@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: py-setuptools | ----------------------------+------------------- Comment (by port@…): Replying to [comment:5 jmr@…]:

Some of the log looks like your prefix is /usr/local/opt/mports but other parts look like it is /opt/mports. Which is your actual prefix? (And where is the other one coming from?) This is because I've installed from source and somewhere PATHS were wrongly written. Also I've changed permissions. Recently I reinstalled (from source) with this new /opt/local/var/macports/home directory and all works fine. My configuration prefix is /opt/mports but opt is a symlink to /usr/local/opt which is the actual directory of my scripts. There is still a mistmatch in my PATH to /usr/local/opt/mports/share/man, I guess this is what you see in main.log

-- Ticket URL: <https://trac.macports.org/ticket/50244#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X

#50244: port upgrade outdated is unable to upgrade py34-setuptools ----------------------------+------------------- Reporter: port@… | Owner: jmr@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: py-setuptools | ----------------------------+------------------- Comment (by jmr@…): The actual problems appears to be {{{ sh: /opt/mports/Library/Frameworks/Python.framework/Versions/3.4/bin/python3.4: No such file or directory }}} i.e. the executable that should be provided by python34 is apparently missing. -- Ticket URL: <https://trac.macports.org/ticket/50244#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X