Opened 6 years ago

Closed 6 years ago

#58203 closed defect (duplicate)

py37-idna fails to install (no destroot found)

Reported by: mouse07410 (Mouse) Owned by:
Priority: Normal Milestone:
Component: base Version:
Keywords: Cc: stromnov (Andrey Stromnov)
Port: py-idna

Description

MacOS Mojave 10.14.3, Xcode-10.1, Macports-installed python-3.7 (everything up to date)

$ sudo port upgrade outdated && sudo port uninstall inactive
--->  Computing dependencies for py37-idna
--->  Installing py37-idna @2.8_0
Error: Failed to install py37-idna: no destroot found at: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-idna/py37-idna/work/destroot
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-idna/py37-idna/main.log for details.
Error: Problem while installing py37-idna
Error: Follow https://guide.macports.org/#project.tickets to report a bug.

Appears to be a collision between what Python-3.7 installs (other packages, pip-3.7) and what Macports does.

Attempts to activate py37-idna manually fail:

$ sudo port -f activate py37-idna
Error: port activate failed: Registry error: py37-idna is not installed.
$

Basically, I only need this for py37-sphinx, and I'd be happy to keep even sphinx under PIP - question is how.

Attachments (1)

py37-idna.log.txt (12.0 KB) - added by mouse07410 (Mouse) 6 years ago.
Main log

Download all attachments as: .zip

Change History (8)

Changed 6 years ago by mouse07410 (Mouse)

Attachment: py37-idna.log.txt added

Main log

comment:1 Changed 6 years ago by mf2k (Frank Schima)

Port: py-idna added; py37-idna removed
Resolution: invalid
Status: newclosed

comment:2 Changed 6 years ago by mouse07410 (Mouse)

Sorry, the Wiki says that the cure is sudo port clean .... The problem is - it did not help. I get consistent destroy not found after attempts to (re-)install.

comment:3 Changed 6 years ago by mouse07410 (Mouse)

Doing sudo port install -fsn py37-idna resolved the problem.

comment:4 Changed 6 years ago by jmroot (Joshua Root)

If you have precise steps to reproduce the "no destroot found" error, please add them to #55445.

The other problem here was basically ProblemHotlist#xmlwf. Yes, if you install python modules without using the py-* ports (e.g. with pip) but to the same location used by the ports, there will be a file conflict. Don't do that. Forcing the activation will "fix" the issue but leave a bunch of renamed files lying around.

comment:5 Changed 6 years ago by jmroot (Joshua Root)

Summary: py37-idna fails to install (no destroy found)py37-idna fails to install (no destroot found)

comment:6 Changed 6 years ago by jmroot (Joshua Root)

Component: portsbase
Resolution: invalid
Status: closedreopened

comment:7 Changed 6 years ago by jmroot (Joshua Root)

Resolution: duplicate
Status: reopenedclosed
Note: See TracTickets for help on using tickets.