Treat Obsoletes as Conflicts after install
Registered by
Jeff Johnson
RPM 5.4.7 will be treating Obsoletes: as if it were
a Conflicts: assertion after installation.
This SHOULD be mostly transparent because whatever
package has been erased will never fire a persistent
Conflicts: assertion. There are however more complex
behaviors in URPMI depsolving that may need to change because
of the semantic change in RPM 5.4.7 where Obsoletes -> Conflicts
after installation.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Low
- Drafter:
- Jeff Johnson
- Direction:
- Needs approval
- Assignee:
- Per Øyvind Karlsen
- Definition:
- New
- Series goal:
- Accepted for 2012
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
