Ticket #26745 (closed defect: duplicate)
dependency confusion between py26-setuptools and py26-distribute
| Reported by: | jabronson@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | base | Version: | 1.9.1 |
| Keywords: | Cc: | jmr@…, mcalhoun@… | |
| Port: | py26-setuptools |
Description
I just tried doing a port uninstall inactive, and when it got to py26-setuptools, it failed with:
---> Unable to uninstall py26-setuptools 0.6c11_0, the following ports depend on it: ---> py26-virtualenv ---> py26-simplejson ---> py26-jinja2 ---> py26-pygments ---> py26-pyflakes Error: port uninstall failed: Please uninstall the ports that depend on py26-setuptools first.
Next I ran:
$ port info py26-virtualenv py26-virtualenv @1.4.5 (python, devel) Variants: universal ... Library Dependencies: python26, py26-distribute
And lo, py26-setuptools isn't actually listed as a dependency.
I currently have the most up-to-date versions of py26-distribute and py26-setuptools. Please let me know how to get this in order. Ideally I'd only need py26-distribute, and could uninstall py26-setuptools entirely, but I'll settle for whatever keeps everything consistent (that is, not contradicting itself).
Change History
comment:2 in reply to: ↑ 1 Changed 3 years ago by jabronson@…
Replying to raimue@…:
Most probably #13054. Just use force for this one, but consider switching to portdbformat sqlite in your macports.conf.
Before I try with -f, I'd like to see if I can get it working without it. I switched to sqlite, rebuilt the port registry, and ran port uninstall inactive again, but it looks like it cached the failed result. If so, is there a way to clear the cache and try again (without -f)?
comment:3 Changed 3 years ago by jmr@…
- Status changed from new to closed
- Component changed from ports to base
- Resolution set to duplicate
There isn't a "cache" per se. If the deps were wrong in the flat registry, they're still wrong after migrating it to sqlite. They will however be correct after upgrading to a new version of a port when using sqlite.


Most probably #13054. Just use force for this one, but consider switching to portdbformat sqlite in your macports.conf.