Bug 969873

Summary: Unable to update mesa
Product: [Fedora] Fedora Reporter: Benjamin Kahn <bkahn>
Component: dnfAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: akozumpl, packaging-team-maint, pnemade
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-03 07:53:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dnf, then yum update none

Description Benjamin Kahn 2013-06-02 20:34:04 UTC 
Created attachment 756098 [details]
dnf, then yum update

Description of problem:
Tried to update my system using dnf, but could not because of a conflict with mesa. I tried with yum and succeeded.

Version-Release number of selected component (if applicable):
dnf-0.2.23-1.git50db212.fc18.noarch

How reproducible:
Happened every time I tried

Steps to Reproduce:
1. dnf update (fail)
2. yum update (success)

Actual results:
dnf failed to update with this message:
Running Transaction Check
ERROR with transaction check vs depsolve:
mesa-dri-filesystem < 9.2-0.7.20130528.fc18 is obsoleted by mesa-filesystem-9.2-0.7.20130528.fc18.x86_64
To diagnose the problem, try running: 'rpm -Va --nofiles --nodigest'.
To fix inconsistent RPMDB, try running: 'rpm --rebuilddb'.
If the above doesn't help please report this error at 'https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=dnf'.

Expected results:
update success

Additional info:
See attached log
Comment 1 Ales Kozumplik 2013-06-03 07:53:35 UTC 
Hello,

this is already fixed in bug 962188 and should update fine with dnf-0.3.5 or later.

*** This bug has been marked as a duplicate of bug 962188 ***