Bug 735235

Summary: Upgrade fails on transaction error
Product: [Fedora] Fedora Reporter: Barry Fishman <barry>
Component: yumAssignee: Seth Vidal <skvidal>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 16CC: ffesti, james.antill, maxamillion, opossum1er, pmatilai, tim.lauridsen, zpavlas
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: 2011-09-03 14:37:51 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:
Attachments:
Description Flags
Log from yum update --skip-broken none

Description Barry Fishman 2011-09-01 21:18:23 UTC 
Description of problem:
When I try to update with Software Update or Yum I get a popup
that says:

Transaction error 
The GPG keys listed for the "Fedora 16 - x86_64" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.

Was attempting to update the 2011-08-29 and 2011-08-18 changes.
Previous attempts stalled because of missing packages

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

Fedora 16 installed from alpha

How reproducible:

Always.  I tried a 'yum clean all' and restarting with no effect

Steps to Reproduce:
1. Run software update or yum
2.
3.
  
Actual results:
as described.

Expected results:

At least some information about what package failed so I could uninstall it.

Additional info:

Fedora 15 runs fine.
Comment 1 Barry Fishman 2011-09-01 21:31:48 UTC 
Created attachment 521105 [details]
Log from yum update --skip-broken

I've add the output when I run yum.
Comment 2 Barry Fishman 2011-09-02 19:14:28 UTC 
This seems to be the same as bug #735037, which I discovered later.  There seems to be a long delay between filing a but and it showing up.  There seems to be no way for original submitters to merge there bug reports with that of previous reports they discovered later.

I ran the 'Software Update' application and it failed again with the same bug.  I then ran 'yum update --verbose --skip-broken and it succeeded.

I then did another 'yum update --skip-broken' and a few more updates happened.

Now "Software Update' runs without signaling a an error.  Of course, there are still packages that don't update due to missing dependencies.
Comment 3 Barry Fishman 2011-09-03 14:37:51 UTC 
Seem to be the same as a previous bug report, which seems to have
been resolved.

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