This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 455061 - bind.spec uses Patch0: but %patch -p1 - inconsistent behaviour
bind.spec uses Patch0: but %patch -p1 - inconsistent behaviour
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: bind (Show other bugs)
rawhide
All Linux
low Severity medium
: ---
: ---
Assigned To: Adam Tkac
Fedora Extras Quality Assurance
: EasyFix
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-11 15:01 EDT by Robert Scheck
Modified: 2013-04-30 19:40 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-14 04:32:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Robert Scheck 2008-07-11 15:01:33 EDT
Description of problem:
bind.spec uses Patch0: but %patch -p1 - future rpm versions (rpm.org versions) 
will complain about this. Please use either "Patch0:" and "%patch0 -p1" OR use
"Patch:" and "%patch -p1". Just consistent behaviour, not more - thank you.

Version-Release number of selected component (if applicable):
bind-9.5.1-0.1.b1

How reproducible:
Everytime and always, see above.

Actual results:
bind.spec uses Patch0: but %patch -p1 - inconsistent behaviour.

Expected results:
Please use either "Patch0:" and "%patch0 -p1" OR use "Patch:" and "%patch
-p1". Just consistent behaviour.
Comment 1 Robert Scheck 2008-07-11 15:03:45 EDT
--- bind.spec       2008-07-11 20:51:16.000000000 +0200
+++ bind.spec.rsc   2008-07-11 20:59:18.000000000 +0200
@@ -177,7 +177,7 @@
 %setup -q -n %{name}-%{version}%{PREVER}

 # Common patches
-%patch -p1 -b .varrun
+%patch0 -p1 -b .varrun
 %patch1 -p1 -b .key
 %patch5 -p1 -b .nonexec
 %patch10 -p1 -b .PIE
Comment 2 Adam Tkac 2008-07-14 04:32:37 EDT
Fixed in CVS, will be included in next build. Thanks for report

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