Bug 163257 - rpmbuild doesn't complain when script file couldn't be opened
rpmbuild doesn't complain when script file couldn't be opened
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: rpm (Show other bugs)
4
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Paul Nasrat
Mike McLean
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-07-14 11:19 EDT by Simon Perreault
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-07-14 13:30:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Simon Perreault 2005-07-14 11:19:19 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.4; Linux) KHTML/3.4.1 (like Gecko)

Description of problem:
I'm using the -f and -p flags with the %post section of a spec file to have a 
fairly long Perl script be run after my RPM is installed. Initially I didn't 
know where the -f flag would be looking for my file. Should I put it in 
SOURCES, SPECS, or something else? Anyway, I figured that rpmbuild would 
complain until I got it right. 
 
Unfortunately, rpmbuild doesn't complain. Looking at the processScriptFiles() 
function, it looks like it should. However, something is making it not 
complain. It would be nice if it did complain and stop building my RPM. 

Version-Release number of selected component (if applicable):
rpm-4.4.1-21

How reproducible:
Always

Steps to Reproduce:
1. Use this %post section:  
  
%post -p /usr/bin/perl -f %{name}.post  
 
2. Make sure %{name}.post doesn't exist. 
3. Build RPM. 

Actual Results:  Built fine. 

Expected Results:  Rpmbuild should have aborted with an error message saying that it couldn't 
open %{name}.post. 

Additional info:
Comment 1 Simon Perreault 2005-07-14 13:30:22 EDT
It didn't complain because -f doesn't work when not using %setup, which will 
be filed as another bug. 

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