Bug 869481

Summary:	"Package $RPM is not signed" error only reports first package
Product:	[Fedora] Fedora	Reporter:	James Livingston <jlivings>
Component:	yum	Assignee:	Fedora Packaging Toolset Team <packaging-team>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	admiller, ffesti, james.antill, joallen, packaging-team, tim.lauridsen, zpavlas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-05-28 21:02:28 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 James Livingston 2012-10-24 04:13:03 UTC

If you attempt to perform a "yum update" and a package is not signed, it will fail with a "Package $RPM is not signed" error.

If more than one package is not signed, it will only report the first one it encounters. To find out all the packages that aren't signed, you need to then run "yum update -x $PACKAGE" and see if it fails again.

It would be nice if it reported all the unsigned packages when failing with that error, not just the first one.

Comment 1 James Antill 2013-05-28 21:02:28 UTC

 The problem is that the most common configuration is to have a single key for an entire repo. ... and so the entire repo. is either signed or not.
 Thus. it's often not desired to get the warning N times when you are updating N pkgs.

 If you need to do some rel-eng type checking, a tool using the yum API would be much better.