Treat Obsoletes as Conflicts after installation
Registered by
Jeff Johnson
Obsoletes: have traditionally been implemented as an
installation directive rather than a dependency assertion.
This leads to flip-flop-flip behavior where a previously erased
package is then reinstalled by depsolvers using a broken dependency.
Blueprint information
- Status:
- Started
- Approver:
- Jeff Johnson
- Priority:
- High
- Drafter:
- Jeff Johnson
- Direction:
- Approved
- Assignee:
- Jeff Johnson
- Definition:
- Review
- Series goal:
- Accepted for 5.4
- Implementation:
-
Slow progress
- Milestone target:
-
5.4.11
- Started by
- Jeff Johnson
- Completed by
Related branches
Related bugs
| Bug #638604: rpm -Uvh does not consider obsoletes | New |
| Bug #651473: obsoletes cannot be matched in rpm-python interface | New |
Sprints
Whiteboard
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
