Bug 843579 - yum software update error
Summary: yum software update error
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 17
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Fedora Packaging Toolset Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-26 16:46 UTC by dylan
Modified: 2014-01-21 23:23 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-21 20:03:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description dylan 2012-07-26 16:46:52 UTC
Description of problem:
When update software,get the following error:

ERROR with transaction check vs depsolve:
mesa-dri-filesystem(x86-32) is needed by mesa-dri-drivers-8.0.3-3.fc17.i686
libcups.so.2 is needed by gtk2-2.24.11-1.fc17.i686
libcups.so.2 is needed by gtk3-3.4.4-1.fc17.i686
Please report this error at https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=rawhide&component=yum

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Antti Huhtala 2012-08-02 21:51:02 UTC
Same thing here when trying to update my F16 -> F17 upgraded (from Fedora 17 x86_64 DVD) system. When I removed those three 32-bit packages from the update list, a new error was generated:

Protected multilib versions: gtk2-2.24.11-1.fc17.x86_64 != gtk2-2.24.8-3.fc16.i686
Protected multilib versions: gtk3-3.4.4-1.fc17.x86_64 != gtk3-3.2.4-1.fc16.i686 : Protected multilib versions: gtk2-2.24.11-1.fc17.x86_64 != gtk2-2.24.8-3.fc16.i686
Protected multilib versions: gtk3-3.4.4-1.fc17.x86_64 != gtk3-3.2.4-1.fc16.i686

Removing the 64-bit packages from update list did not help; the original error message (reported by dylan above) was generated.

Comment 2 James Antill 2013-05-21 20:03:43 UTC
Look at the output of "yum check" and solve all those problems, then it should work fine.


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