Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#45801 closed defect (invalid)

py27-markupsafe fails because it doesn't install dependencies

Reported by: vlsd (Vlad) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.3.2
Keywords: Cc:
Port: py27-markupsafe

Description

I'm on Yosemite and I get errors like this:

:debug:install Error code: NONE
:debug:install Backtrace: no destroot found at: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-markupsafe/py27-markupsafe/work/destroot
    while executing
"create_archive $location $portarchivetype"
    (procedure "portinstall::install_main" line 22)
    invoked from within
"portinstall::install_main org.macports.install"
    ("eval" body line 1)
    invoked from within
"eval $procedure $targetname"
:info:install Warning: targets not executed for py27-markupsafe: org.macports.activate org.macports.install
:error:install Failed to install py27-markupsafe
:debug:install Registry error: xorg-printproto not registered as installed & active.
    invoked from within
"registry_active $subport"
    invoked from within
"$workername eval registry_active \$subport"

I can install xorg-printproto but then I get the same error except for a different port. Shouldn't be these installed automatically?

Change History (2)

comment:1 in reply to:  description Changed 10 years ago by larryv (Lawrence Velázquez)

Keywords: dependencies removed
Resolution: invalid
Status: newclosed

Replying to vloodo@…:

:debug:install Error code: NONE
:debug:install Backtrace: no destroot found at: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-markupsafe/py27-markupsafe/work/destroot
    while executing
"create_archive $location $portarchivetype"

The problem has nothing to do with dependency resolution. MacPorts is trying to finish up an installation, but there’s no destroot at the location where it’s expecting to find one. It sounds like this is the case for multiple ports. I don’t know how your setup managed to get into this situation, but you should clean up to reset this incorrect state.

$ sudo port clean all

comment:2 Changed 10 years ago by vlsd (Vlad)

Yeah, I just figured that out right after I posted the ticket. Thanks for closing!

Note: See TracTickets for help on using tickets.