Conflicts: dependency assertions with missing release misfire
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| RPM |
New
|
Undecided
|
Unassigned | ||
| rpm (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: rpm
The Mancoosi WP5 Project discovered a bug in RPM last November,
comparing apt and rpm assertion checkers.
The bug affects all versions of RPM. A Conflicts: assertion with
a missing value in the Release: field returns FALSE instead of TRUE.
Conflicts: assertions that explicitly include a Release: have the correct value.
Since the bug has never been reported against RPM (in the ~10 years the
bug has been present) its still not clear
what the final resolution will be.
The choices to fixing are pretty clear:
1) remain "bug compatible" with all existing releases of RPM.
The corollary here will be to detect and forbid Conflicts: without an explicit Release:
2) retrofit a fix (as Mandriva has attempted) to be logically consistent with assertions.
The "fix" isn't hard and is known. This path will be what @rpm5.org does as soon as
its clear what legacy compatibility issues need to be solved and implemented.
