Bug 682453 - openbios won't update
Summary: openbios won't update
Keywords:
Status: CLOSED DUPLICATE of bug 679179
Alias: None
Product: Fedora
Classification: Fedora
Component: openbios
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Glauber Costa
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-05 16:59 UTC by darrell pfeifer
Modified: 2011-03-06 13:04 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-03-06 13:04:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description darrell pfeifer 2011-03-05 16:59:22 UTC
Description of problem:

openbios won't update properly


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


How reproducible:


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


Expected results:


Additional info:


--> Running transaction check
---> Package openbios-common.noarch 0:1.0-2.fc12 will be updated
--> Processing Dependency: openbios-common = 1.0-2.fc12 for package: openbios-ppc-1.0-2.fc12.noarch
---> Package openbios-common.noarch 0:1.0-4.1031.fc16 will be an update
--> Finished Dependency Resolution
Error: Package: openbios-ppc-1.0-2.fc12.noarch (@/openbios-ppc-1.0-2.fc12.noarch)
           Requires: openbios-common = 1.0-2.fc12
           Removing: openbios-common-1.0-2.fc12.noarch (installed)
               openbios-common = 1.0-2.fc12
           Updated By: openbios-common-1.0-4.1031.fc16.noarch (koji)
               openbios-common = 1.0-4.1031.fc16
           Available: openbios-common-1.0-3.fc15.noarch (kojif15)
               openbios-common = 1.0-3.fc15
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

I have tried removing (which removes qemu) and re-installing but the error persists.

Comment 1 Vaclav "sHINOBI" Misek 2011-03-06 13:04:08 UTC

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


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