#8431 closed defect (fixed)
BUG: port uninstall can't resolve dependencies
| Reported by: | namely_void@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | MacPorts 2.0.2 |
| Component: | base | Version: | |
| Keywords: | Cc: | ezra.story@… | |
| Port: |
Description
Doing a "port uninstall installed" cannot resolve dependencies and uninstall "from the top down" as it should. Instead, it aborts on the first port that has dependant ports.
Change History (12)
comment:1 Changed 14 years ago by pipping@…
| Milestone: | → Port Bugs |
|---|
comment:2 Changed 14 years ago by pipping@…
| Milestone: | Port Bugs → MacPorts 1.4 |
|---|
comment:3 Changed 14 years ago by jmpp@…
| Milestone: | MacPorts 1.4 → Needs developer review |
|---|---|
| Priority: | Expected → Important |
comment:4 Changed 14 years ago by jmpp@…
| Owner: | changed from macports-tickets@… to macports-dev@… |
|---|
comment:5 Changed 14 years ago by jmpp@…
| Milestone: | Needs developer review → MacPorts base bugs |
|---|
Milestone Needs developer review deleted
comment:6 Changed 14 years ago by nox@…
| Priority: | Important → High |
|---|---|
| Version: | 1.2 |
comment:7 Changed 13 years ago by jmroot (Joshua Root)
| Cc: | ezra.story@… added |
|---|
Cc reporter of duplicate #14834.
comment:8 Changed 12 years ago by tobypeterson
| Milestone: | MacPorts base bugs → MacPorts Future |
|---|
Milestone MacPorts base bugs deleted
comment:9 Changed 12 years ago by jmroot (Joshua Root)
| Priority: | High → Normal |
|---|
comment:10 Changed 11 years ago by jmroot (Joshua Root)
Do we want to call this fixed given that sudo port uninstall --follow-dependents installed will now succeed in uninstalling everything?
comment:11 Changed 10 years ago by jmroot (Joshua Root)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:12 Changed 10 years ago by jmroot (Joshua Root)
| Milestone: | MacPorts Future → MacPorts 2.0.2 |
|---|
Note: See
TracTickets for help on using
tickets.
This is one of the many shortcomings of our dependency engine, so the ticket has no place in the 1.4 milestone which is less than two days away. Setting to "needs dev review" so that discussion on it places it elsewhere, but in short I don't see this being fixed without a major rework of our deps engine.
-jmpp