RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Running rpmbuild ... --sign --define '_gpg_name XXXXXXXX' fails asking to have the %_gpg_name defined in rpmmacros.

Version-Release number of selected component (if applicable):
$ rpm -qa rpm\*
rpm-python-4.11.1-16.el7.x86_64
rpm-4.11.1-16.el7.x86_64
rpm-build-libs-4.11.1-16.el7.x86_64
rpm-build-4.11.1-16.el7.x86_64
rpm-sign-4.11.1-16.el7.x86_64
rpmlint-1.5-4.el7.noarch
rpm-libs-4.11.1-16.el7.x86_64


How reproducible:
Always. This same Makefile/command sequence worked just fine in RHEL 6.5

Steps to Reproduce:
1. Empty ~/.rpmmacros
2. rpmbuild -D "version $(VERSION)" -D "release $(RELEASE)" -ta --clean --sign --define '_gpg_name XXXXXXXX' file.tar.gz

Actual results:
You must set "%_gpg_name" in your macro file


Expected results:
Should prompt for passphrase and sign the package.

Additional info:

If I break the command in two:
rpmbuild -D "version $(VERSION)" -D "release $(RELEASE)" -ta --clean file.tar.gz
rpmsign --addsign --define '_gpg_name XXXXXXXX' $(BUILDDIR)/RPMS/$(ARCH)/$(FULLNAME).$(ARCH).rpm

It works.

I am presuming that the --define is not "passed" from rpmbuild to rpmsign when this is combined? If so, this is a regression from RHEL 6.

Signing support was removed from rpmbuild deliberately. "rpmbuild --sign" is just popt alias to allow basic stuff to work. But it can be removed in the future. You should use command rpmsign for signing of rpm packages. We will add a deprecation warning to the description of "--sign" in output of "rpmbuild --help".

I add devel_ack for this deprecation warning.

Lubos, 
should I clone this bug also for RHEL-6? Would you add the same warning to RHEL 6 too?

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-2015-2138.html

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days