Bug 79184
Summary: | Incorrect dependency computation when upgrading KDE packages | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Alexandre Oliva <aoliva> |
Component: | kdelibs | Assignee: | Than Ngo <than> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | jbj, mitr |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-12-22 12:43:00 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alexandre Oliva
2002-12-06 21:27:17 UTC
Packaging problem, kdelibs-devel Requires: needs an explicit epoch. bash$ rpm -qp --requires kdelibs-devel-3.0.3-8.3.i386.rpm qt-devel >= 3.0.5 kdelibs = 3.0.3 ... Note: As written, this is the same as Requires: kdelibs = 0:3.0.3 but needs to be Requires: kdelibs = 6:3.0.3 bash$ rpm -qp --provides kdelibs-3.0.3-8.3.i386.rpm ... kdelibs = 6:3.0.3-8.3 Well, then... The rpm bug is that it does *NOT* complain about the unsatisfied 0:3.0.3 dependency when I upgrade both kdelibs and kdelibs-devel at the same time, right? rpm doesn't complain about a lot of things that it should. FWIW, try rpm -Vav to see all the busted dependencies like kdelibs-devel. And, for extra credit, add (undocumented) --promoteepoch to the set of packages above. The issue is how a non-specified Epoch: should be treated, either in the same Epoch: (behavior with --promoteepoch), or as equivalent to Epoch: 0. I choose to treat a missing Epoch: as Epoch: 0, as that makes sense. Too bad that breaks some packaging, there's been a policy in place since Red Hat 6.2 to always specify the Epoch: in a Requires: if the corresponding Provides: has an Epoch: And, yes, added packages are Epoch: promoted (i.e. missing Epoch: disables Epoch: comparison), while the same package, after being installed, is treated as Epoch: 0. i wonder why this issue was not found by QA? ok, anaway i'm waiting for next security fix in next days, so i will do a new kde errata. it's fixed in 3.0.5a-1, which will be released as errata soon |