Bug 1106912 - Wrong gpg key symlinks
Summary: Wrong gpg key symlinks
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: generic-release
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-09 18:12 UTC by Tom Atkinson
Modified: 2014-06-19 22:57 UTC (History)
2 users (show)

Fixed In Version: generic-release-20-4
Clone Of:
Environment:
Last Closed: 2014-06-19 22:57:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tom Atkinson 2014-06-09 18:12:42 UTC
generic-release provides /etc/yum.repos.d/fedora-updates.repo which has

gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch

The file /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-20-x86_64 does not exist, so package signature checking fails.

I believe it wants these changes ported over from fedora-release:

http://pkgs.fedoraproject.org/cgit/fedora-release.git/commit/fedora-release.spec?h=f20&id=ec261037dddf854c6ca7ec60a7df283382149eea

Comment 1 Fedora Update System 2014-06-09 18:59:03 UTC
generic-release-20-4 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/generic-release-20-4

Comment 2 Tom Atkinson 2014-06-09 19:33:31 UTC
Excellent, thanks.

Comment 3 Fedora Update System 2014-06-11 16:30:10 UTC
Package generic-release-20-4:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing generic-release-20-4'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-7255/generic-release-20-4
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2014-06-19 22:57:27 UTC
generic-release-20-4 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


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