Bug 162816
Summary: | package-cleanup --problems misdiagnosing unversioned provides | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Christopher Stone <tkmame> |
Component: | yum-utils | Assignee: | Seth Vidal <skvidal> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | Christian.Iseli, tim.lauridsen |
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: | 2007-02-14 10:25:27 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
Christopher Stone
2005-07-08 21:59:43 UTC
Just to elaborate. For the Package redhat-artwork requires redhat-logos >= 1.1.10 error on fc4 rpm -q --provides fedora-logos redhat-logos <--------- unversioned system-logos fedora-logos = 1.1.31-1 rpm -q --requires redhat-artwork <------------ versioned redhat-logos >= 1.1.22 A simple test of how rpm actually handles this version/unversioned mismatch rpm -e --nodeps redhat-artwork rpm -ivv redhat-artwork-0.122-10.i386.rpm 2> /tmp/install.log from the install.log: D: Requires: redhat-logos >= 1.1.22 YES (db provides) rpm -q --whatprovides redhat-logos fedora-logos-1.1.31-1 fedora-logos package is the only thing providing redhat-logos and rpm sees the unversioned provides as filling the versioned requires. upgrade to yum 2.3.3 or above and tell me if the above issue goes away. I don't know if this was actually fixed, but package-cleanup --problems seems to be working fine now. FC3 and FC4 have now been EOL'd. Please check the ticket against a current Fedora release, and either adjust the release number, or close it if appropriate. Thanks. Your friendly BZ janitor :-) According to #3, it package-cleanup was working. |