Treat Obsoletes as Conflicts after installation

Registered by Jeff Johnson on 2012-01-11

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:
milestone icon 5.4.11
Started by
Jeff Johnson on 2012-02-17

Whiteboard

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.