py27-pycparser update fails due to leftover files

[jfcaron3]

It looks like py27-pycparser doesn't clean up after itself somehow. While doing a regular upgrade outdated I got an error, but since I noticed py27-pycparser didn't have any dependents I tried uninstalling it (which worked), but then the upgrade still didn't work. After an uninstall and a clean, I still get this error:

[10:24]~/Projects/Mu2e/LabView/Data$ sudo port uninstall py27-pycparser
Password:
--->  Uninstalling py27-pycparser @2.14_0
--->  Cleaning py27-pycparser
[10:27]~/Projects/Mu2e/LabView/Data$ sudo port upgrade outdated
--->  Computing dependencies for py27-pycparser
--->  Installing py27-pycparser @2.14_0
Error: org.macports.install for port py27-pycparser returned: no destroot found at: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-pycparser/py27-pycparser/work/destroot
Please see the log file for port py27-pycparser for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-pycparser/py27-pycparser/main.log
Error: Problem while installing py27-pycparser
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets

[jfcaron3]

main.log

[jfcaron3]

Doing more investigation, this seems to be related to an undeclared dependency of py27-paramiko for some reason. The reasoning: I upgraded one at a time all my other outdated ports successfully except py27-paramiko. This one fails because it automatically tries to first update py27-pycparser, even if py27-pycparser is not installed. Neither port refers to the other in the rdeps/rdependencies list.

[mf2k (Frank Schima)]

What is the output of the following?

port installed py27-pycparser

[jfcaron3]

After doing "port uninstall py27-pycparser" it says it's not installed, but then when I try to upgrade py27-paramiko, I get the same error again:

[16:23]~/Projects/Proto2BeamTest2$ sudo port uninstall py27-pycparser
Password:
--->  Uninstalling py27-pycparser @2.14_0
--->  Cleaning py27-pycparser
[16:23]~/Projects/Proto2BeamTest2$ port installed py27-pycparser
None of the specified ports are installed.
[16:23]~/Projects/Proto2BeamTest2$ sudo port upgrade py27-paramiko
--->  Computing dependencies for py27-pycparser
--->  Installing py27-pycparser @2.14_0
Error: org.macports.install for port py27-pycparser returned: no destroot found at: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-pycparser/py27-pycparser/work/destroot
Please see the log file for port py27-pycparser for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-pycparser/py27-pycparser/main.log
Error: Problem while installing py27-pycparser
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets

[mf2k (Frank Schima)]

Your output implies that the port was not actually cleaned. The following should work.

sudo port clean py27-pycparser
sudo port install py27-pycparser

[mf2k (Frank Schima)]

FYI, py27-pycparser is an indirect dependency (through other dependencies) for py27-paramiko.

[jfcaron3]

I guess I forgot how to check what ports depend on others: how come "port dependents py27-pycparser" says "has no dependents."?

Even after cleaning, I cannot install py27-pycparser (either by directly installing it, or by trying to update py27-paramiko):

[16:28]~/Projects/Proto2BeamTest2$ sudo port clean py27-pycparser
--->  Cleaning py27-pycparser
[16:28]~/Projects/Proto2BeamTest2$ sudo port install py27-pycparser
--->  Computing dependencies for py27-pycparser
--->  Fetching archive for py27-pycparser
--->  Attempting to fetch py27-pycparser-2.14_0.darwin_13.noarch.tbz2 from https://packages.macports.org/py27-pycparser
--->  Attempting to fetch py27-pycparser-2.14_0.darwin_13.noarch.tbz2.rmd160 from https://packages.macports.org/py27-pycparser
--->  Installing py27-pycparser @2.14_0
--->  Activating py27-pycparser @2.14_0
Error: org.macports.activate for port py27-pycparser returned: Image error: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pycparser-2.14-py2.7.egg-info already exists and does not belong to a registered port.  Unable to activate port py27-pycparser. Use 'port -f activate py27-pycparser' to force the activation.
Please see the log file for port py27-pycparser for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-pycparser/py27-pycparser/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port py27-pycparser failed

I only have one version of pycparser installed:

[16:28]~/Projects/Proto2BeamTest2$ port installed|grep cparser
  py27-pycparser @2.14_0

[mf2k (Frank Schima)]

Your ports directory got munged somehow. Perhaps a 3rd party installer? As the output says, you need to force the activation.

sudo port -f activate py27-pycparser

[jfcaron3]

I have not used any 3rd-party installers for this port, as far as I know.

I thought I had tried the forced activation before and it failed. This time it gave a ton of errors about moving files around in site-packages.

I don't know what's going on anymore. After forced activation "port dependents py27-pycparser" now tells me that py27-cffi is a dependent. I was able to uninstall py27-cffi and then py27-pycparser. Now when I do "port upgrade outdated" it once again tries to pull in py27-pycparser and fails with the same error message as in comment#4: "no destroot".

[jfcaron3]

I found a sequence that does something: -force activation of the offending port (e.g. py27-pycparser).
-uninstall offending port.
-clean offering port.
-Try to upgrade outdated ports again. Now the same initial error occurs but for some other port up the dependency chain (py27-cffi, then py27-asn1, now py27-idna).

I think I am working my way up the whole dependency tree of python27. What could have caused this? Is there a way to short-circuit this chain and get back to my life?

[mf2k (Frank Schima)]

Since Trac is not for tech support, bring up your issue(s) on the Macports Users mailing list instead.