Bug 1293483

Summary:	rpmbuild ignores --sign if --quiet is used.
Product:	Red Hat Enterprise Linux 7	Reporter:	Karl Hastings <kasmith>
Component:	rpm	Assignee:	Florian Festi <ffesti>
Status:	CLOSED ERRATA	QA Contact:	Karel Srot <ksrot>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.2	Keywords:	Regression, TestBlocker
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rpm-4.11.3-21.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-04 04:38:48 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 Karl Hastings 2015-12-21 21:46:13 UTC

Description of problem:
rpmbuild in RHEL7 does not prompt for the signing key passphrase, or seemingly attempt in any way to sign the rpm if --quiet is passed on the command line.

Since rpmbuild is *very* verbose and --quiet does *not* mean "no output" it seems to be a bug that it doesn't attempt to sign the rpm.

Version-Release number of selected component (if applicable):
rpm-build-4.11.3-17.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. rpmbuild --sign -bb --quiet somefile.spec

Actual results:
rpm is built but not signed

Expected results:
rpmbuild asks for the passphrase and generates a signed .rpm

Additional info:

Comment 2 Thomas Woerner 2015-12-29 12:20:12 UTC

Reassigning to rpm.

Comment 6 Florian Festi 2016-07-04 16:25:08 UTC

The signing code uses the output of rpmbuild which is silent by --quiet. Increased the priority of the list of generated packages.

Generally rpmbuild --sign should be avoided and the new rpmsign utility should be used.

Comment 12 errata-xmlrpc 2016-11-04 04:38:48 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2359.html