Bug 262841 - Public key for perl-PDF-API2-0.62-2.fc7.noarch.rpm is not installed
Summary: Public key for perl-PDF-API2-0.62-2.fc7.noarch.rpm is not installed
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-PDF-API2
Version: 7
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bernard Johnson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-08-29 09:44 UTC by Emmanuel Seyman
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-08-29 13:47:17 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Emmanuel Seyman 2007-08-29 09:44:44 UTC 
Description of problem:
The latest update to perl-PDF-API2 seems to have been signed with the rawhide key

Version-Release number of selected component (if applicable):
0.62-2.fc7

How reproducible:
always

Steps to Reproduce:
1. Run 'yum update'
2. See yum try to install perl-PDF-API2
3. See yum fail to install perl-PDF-API2 with the error message :
   Public key for perl-PDF-API2-0.62-2.fc7.noarch.rpm is not installed

Actual results:
Yum fails to update the rpm

Expected results:
Yum should update the rpm
Comment 1 Bernard Johnson 2007-08-29 13:34:03 UTC 
Strange.  That was after I got this email:

Package: perl-PDF-API2
NVR: perl-PDF-API2-0.62-2.fc7
User: bodhi
Status: failed
Tag Operation: moved
From Tag: dist-fc7-updates-testing
Into Tag: dist-fc7-updates

perl-PDF-API2-0.62-2.fc7 unsuccessfully moved from dist-fc7-updates-testing into
dist-fc7-updates by bodhi
Operation failed with the error:
    koji.TagError: build perl-PDF-API2-0.62-2.fc7 not in tag
dist-fc7-updates-testing


I'll see if rel-eng can shed any light on this.
Comment 2 Bernard Johnson 2007-08-29 13:47:17 UTC 
It seems that rel-eng has signed it with the correct key now, so I'm closing
this ticket.

They are still looking into the cause though.
Note You need to log in before you can comment on or make changes to this bug.