Opened 8 years ago
Closed 6 years ago
#52320 closed defect (duplicate)
Error: Processing of port py35-setuptools failed
Reported by: | ForeverTangent@… | Owned by: | jmroot (Joshua Root) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 2.3.4 |
Keywords: | Cc: | ||
Port: | py-setuptools |
Description (last modified by mf2k (Frank Schima))
Trying to install scipy of Python35.
It needs Setuptools
I run:
sudo port install py35-setuptools
and I get all this...
Error: org.macports.install for port py35-setuptools returned: no destroot found at: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-setuptools/py35-setuptools/work/destroot Please see the log file for port py35-setuptools for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-setuptools/py35-setuptools/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port py35-setuptools failed
Change History (9)
comment:1 Changed 8 years ago by mf2k (Frank Schima)
Keywords: | Broken Port removed |
---|---|
Owner: | changed from macports-tickets@… to jmr@… |
Port: | py-setuptools added; py35-setuptools removed |
comment:2 Changed 8 years ago by mf2k (Frank Schima)
Description: | modified (diff) |
---|
comment:3 Changed 8 years ago by jmroot (Joshua Root)
It's easy enough to get out of this state by cleaning the port, but I would like to know how you got into it in the first place. Apparently the statefile says that the destroot phase is complete, but the destroot directory does not exist. That shouldn't happen.
comment:4 Changed 8 years ago by ForeverTangent@…
If I install py-scipy... it only seems to install the Python27 of spicy.
If I install py35-scipy, then everything fails.
Not sure how I got in that state either. All I ever run, is "port install/uninstall/clear/installed/list".
Do I need to completely reinstall MacPorts or something?
comment:5 Changed 8 years ago by jmroot (Joshua Root)
Did you clean the port that is actually producing the error, py35-setuptools?
comment:6 Changed 8 years ago by ForeverTangent@…
ARGH!!!
This is so annoying. I swear I ran 'clean' for py-scipy py-setuptools py35-scipy and py35-setuptools before I submitted the ticket.
But I just did all four again... and everything installed cleanly...
Ugh... sigh.
comment:7 Changed 8 years ago by jmroot (Joshua Root)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
OK, so you have a workaround. There's probably a bug in base here, but without steps to reproduce the problem it's impossible to debug. So, I'm closing this ticket.
comment:8 Changed 6 years ago by jmroot (Joshua Root)
Component: | ports → base |
---|---|
Resolution: | worksforme |
Status: | closed → reopened |
comment:9 Changed 6 years ago by jmroot (Joshua Root)
Resolution: | → duplicate |
---|---|
Status: | reopened → closed |
In the future, please use WikiFormatting and Cc the port maintainers (
port info --maintainers py35-setuptools
), if any.