Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1084309 - %autosetup does not apply any patches
%autosetup does not apply any patches
Product: Fedora
Classification: Fedora
Component: rpm (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: packaging-team-maint
Fedora Extras Quality Assurance
: Triaged
Depends On:
Blocks: 1359084 1438815
  Show dependency treegraph
Reported: 2014-04-04 02:58 EDT by Till Maas
Modified: 2017-04-04 09:27 EDT (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1359084 (view as bug list)
Last Closed: 2015-04-10 11:51:15 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Till Maas 2014-04-04 02:58:51 EDT
Patches are specified in the spec but not applied, see e.g.:

curl --silent http://kojipkgs.fedoraproject.org/packages/xdg-utils/1.1.0/0.21.rc2.fc20/data/logs/noarch/build.log  | grep -i patch

This affects F19, F20 and Rawhide.
Comment 1 Till Maas 2014-04-04 02:59:29 EDT
Btw. if you do not have the time, I can take a look.
Comment 2 Rex Dieter 2014-04-04 05:01:04 EDT
It looks like an rpm buglet where %autosetup fails to apply patches in some circumstances (for example, if BuildArch: comes before Patch: declarations).

should be fixed in xdg-utils-1.1.0-0.22

* Fri Apr 04 2014 Rex Dieter <rdieter@fedoraproject.org> 1.1.0-0.22.rc2
- drop using %%autosetup (it didn't work?)
Comment 3 Rex Dieter 2014-04-04 08:01:59 EDT
See details in comment #2, and confirmed in #fedora-devel with mrunge earlier today, %autosetup fails to apply any patches , in particular, %{patches} is empty, if
appears before

The specific case I ran into was:

and moving BuildArch: after all the Patch...: entries made it work.
Comment 4 Panu Matilainen 2014-04-04 08:25:40 EDT
Yup, known. Its one of the lovely wtf quirks caused by the way spec parse recurses on BuildArch.
Comment 5 Ľuboš Kardoš 2015-04-10 11:51:15 EDT
Fixed upstream as 344f938670b8f7400ef177945cef5552783d450f.
Comment 6 Rex Dieter 2015-11-15 09:53:29 EST
For anyone else who hits this in fedora, it appears this got fixed only in f23's rpm, f22 seems to still suffer from it (I had a f22 build fail just now due to unapplied patches)

Note You need to log in before you can comment on or make changes to this bug.