Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1225118

Summary: %autosetup macro erroneously includes the line that follows it
Product: Red Hat Enterprise Linux 7 Reporter: Tadej Janež <tadej.j>
Component: rpmAssignee: Florian Festi <ffesti>
Status: CLOSED ERRATA QA Contact: Karel Srot <ksrot>
Severity: high Docs Contact:
Priority: high    
Version: 7.3CC: ffesti, ksrot, sgraf
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rpm-4.11.3-16.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 11:58:42 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:
Attachments:
Description Flags
Failed build.log for package bup none

Description Tadej Janež 2015-05-26 15:39:40 UTC
Created attachment 1030005 [details]
Failed build.log for package bup

Description of problem:
I'm using the %autosetup macro to automatically apply patches included in the SPEC file: https://github.com/tjanez/bup-package/blob/b195a10a7840ae756b07d0955333b726451887b6/bup.spec#L76

When building my package for EPEL 7 (and Fedora 20), the build step fails since %autosetup also tries to include the line that follows it in the SPEC file (https://github.com/tjanez/bup-package/blob/b195a10a7840ae756b07d0955333b726451887b6/bup.spec#L77) when applying the patches:

+ /usr/bin/git commit -q -a -m 0005-Remove-support-for-par2-due-to-issues-with-the-versi.patch --author 'rpm-build <rpm-build>cp' /builddir/build/SOURCES/README.Fedora .
fatal: Paths with -a does not make sense.

For the complete build log, see the attached build.log.

How reproducible:
Always

Actual results:
%autosetup macro feeds the line that follows it in the SPEC file to its patch management program (git).

Expected results:
%autosetup macro shouldn't feed the line that follows it in the SPEC file to its patch management program (git).

Additional info:
The same SPEC file (or SRPM) builds fine on Fedora 21+ (see: https://copr-be.cloud.fedoraproject.org/results/tadej/bup/)

I found a work-around for this bug: If I insert an empty line after the %autosetup macro, it builds fine.

Comment 2 Florian Festi 2015-07-07 15:49:45 UTC
Fixed upstream a while ago as 1bdcd0500865efd3566efd7f951228f69b58e755
See also #1045723

Comment 10 errata-xmlrpc 2015-11-19 11:58:42 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-2015-2138.html