Bug 1023468

Summary:	[Request] Put all repository's publics keys inside a package.
Product:	[Fedora] Fedora	Reporter:	Gendre Sébastien <paradoxe>
Component:	fedora-release	Assignee:	Dennis Gilmore <dennis>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	20	CC:	dennis, ffesti, jzeleny, novyjindrich, packaging-team-maint, pknirsch, pmatilai
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:	2013-11-14 03:38:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gendre Sébastien 2013-10-25 13:36:42 UTC

Actually, when you upgrade a Fedora n to n+1, you need to manually import the public PGP key using by packages in the news repositories. 

This step can be avoided by putting all publics PGP keys used by Fedora project (on all these actives repositories) inside one package available in repo to all version of Fedora.

With this, when the repositories of the futur version of Fedora are available, users under stables versions of Fedora only needs to update their systems to have the new PGP key. So, if they want to upgrade to new version of Fedora, they only need to lanch fedup.

Comment 1 Panu Matilainen 2013-10-28 08:13:23 UTC

This has nothing to do with rpm itself. fedora-release is where all the public keys are currently stored, reassigning...

That said, having to importing a new pubkey at the time of distro upgrade doesn't seem like a particularly big inconvenience to me.

Comment 2 Dennis Gilmore 2013-11-14 03:38:45 UTC

We started shipping the next releases gpg keys awhile ago now.