Opened 9 years ago
Closed 7 years ago
#50244 closed defect (duplicate)
port upgrade outdated is unable to upgrade py34-setuptools
| Reported by: | port@… | Owned by: | jmroot (Joshua Root) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.4 |
| Keywords: | Cc: | ||
| Port: | py-setuptools |
Description (last modified by mf2k (Frank Schima))
$ port upgrade outdated ---> Computing dependencies for py34-setuptools ---> Building py34-setuptools Error: org.macports.build for port py34-setuptools returned: command execution failed
Attachments (3)
Change History (12)
comment:1 Changed 9 years ago by mf2k (Frank Schima)
| Cc: | jmr@… openmaintainer@… removed |
|---|---|
| Owner: | changed from macports-tickets@… to jmr@… |
| Port: | py-setuptools added; py34-setuptools removed |
comment:2 Changed 9 years ago by mf2k (Frank Schima)
| Description: | modified (diff) |
|---|
In the future, please use WikiFormatting.
comment:3 Changed 9 years ago by jmroot (Joshua Root)
This is an incomplete log, please clean and generate a complete one.
Changed 9 years ago by port@…
| Attachment: | upgrade_outdated_debug.txt added |
|---|
port -d upgrade outdated
comment:4 Changed 9 years ago by port@…
Apparently this is not an issue on py-* port or others but a misconfiguration known and reported in #49101
The solution described worked for me :
% sudo mkdir -p /opt/local/var/macports/home % sudo chown macports:macports /opt/local/var/macports/home
comment:5 follow-up: 6 Changed 9 years ago by jmroot (Joshua Root)
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?)
comment:6 Changed 9 years ago by port@…
Replying to 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
Changed 9 years ago by port@…
| Attachment: | macports.conf added |
|---|
comment:8 Changed 9 years ago by jmroot (Joshua Root)
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.
comment:9 Changed 7 years ago by jmroot (Joshua Root)
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Not entirely sure I'm convinced this is a dupe, but closing as per comment:4.
Please do not Cc openmaintainer@… because it is not a valid email address.