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:

Any chance the %autosetup macro could be added to the EL6 rpm?  Or should EPEL just add it somewhere else?

Version-Release number of selected component (if applicable):
rpm-4.8.0-47.el6

Not sure if we want to backport %autosetup to rhel6 rpm. But %autosetup is not hardcoded in rpm, it is implemented by macros. That means you can easily add %autosetup to your system by adding the content of the attached file into your ~/.rpmmacros or create some file in /etc/rpm and put the content there (then it will be available for all users).

Is that acceptable solution for you?

Created attachment 1100923 [details]
autosetup_macros extracted from /usr/lib/rpm/macros

The goal is to allow Fedora/EPEL rpms to share the same spec file.  If it's not going to be added to RHEL's rpm macros, we can add it to epel-release or similar.

We want to have macros like this in one place. Devel ack for adding autosetup macros into rpm package.

I was just CC'd on this.  epel-rpm-macros has autosetup currently, but if it's going into some base RHEL release then we can remove it.  The question is, when should this happen?

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-0936.html