Bug 602375 - Yum performed incorrect N-V-R comparison for NetworkManager
Summary: Yum performed incorrect N-V-R comparison for NetworkManager
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-09 18:10 UTC by Michel Alexandre Salim
Modified: 2014-01-21 23:15 UTC (History)
5 users (show)

Clone Of:
Last Closed: 2010-06-09 18:41:25 UTC

Attachments (Terms of Use)

Description Michel Alexandre Salim 2010-06-09 18:10:16 UTC
Description of problem:
During the F-13 beta process, the following packages were shipped:

These were upgraded in F-13 final:
NetworkManager to 0.8.1-0.1.git20100510.fc13.x86_64
initscripts to 9.12-1.fc13.x86_64

However, using yum to update NetworkManager fails, apparently 0.8.0 ">=" 0.8.1. updating initscripts fails as it conflicts with NM 0.8.0 (so the failure to update NM blocks the initscripts update).

Updating via rpm -Uvh works as expected

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Download the older NM and initscripts RPMs from Koji
2. rpm -Uvh --oldpackage them
3. yum update NetworkManager
4. yum update initscripts
Actual results:
#3 does not update anything. #4 fails because of file conflicts with NM.

Expected results:
Should work fine

Additional info:

Comment 1 seth vidal 2010-06-09 18:18:52 UTC
you need to provide A LOT more information here.

Specifically what is the failure that you received from yum?

Comment 2 seth vidal 2010-06-09 18:34:04 UTC
yum --disablerepo=updates list initscripts NetworkManager\*

Comment 3 James Antill 2010-06-09 18:41:25 UTC
As I said in email, it's not a yum bug if you exclude packages and then can't update them.

Comment 4 Michel Alexandre Salim 2010-06-10 07:49:01 UTC
Apologies -- turns out I did add an exclusion back in March, and had forgotten about it in the meantime.

Note You need to log in before you can comment on or make changes to this bug.