Bug 501747

Summary: Package rpcbind-0.1.7-3.fc11.i586.rpm is not signed
Product: [Fedora] Fedora Reporter: Eddie Lania <eddie>
Component: rpcbindAssignee: Steve Dickson <steved>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: gvarisco, steved
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-05-22 17:53:30 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:

Description Eddie Lania 2009-05-20 15:20:20 UTC
Description of problem:Package rpcbind-0.1.7-3.fc11.i586.rpm is not signed


Version-Release number of selected component (if applicable):
Package rpcbind-0.1.7-3.fc11.i586.rpm is not signed

How reproducible:


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


Expected results:


Additional info:

Comment 1 Gianluca Varisco 2009-05-20 21:07:35 UTC
Eddie,

some packages were tagged yesterday and pushed - erroneously -  unsigned. It will be fixed with the next push.

More details are available in this thread: https://www.redhat.com/archives/fedora-test-list/2009-May/thread.html#00935

Comment 2 Eddie Lania 2009-05-21 06:43:31 UTC
Thank you,

But how am I going to solve now the problem in bug 501758 which has been caused by this bug?

All packages that gpk-update tried to update have failed because of the unsigned rpcbind and libtirpc packages and messed up the rpm database so that they no longer appear in the list of packages to update.

I could download them and force reinstall but that is also not possible because I do not have a list of the failed packages so I don't know which packages it were, see bug 501758.

Help me please.

Eddie.

Comment 3 Eddie Lania 2009-05-22 17:49:17 UTC
Solved.

I think you can close this bug.

Thank you.