Bug 184601 - Fails with Fascist Build Policy; Built Files not in SPEC
Fails with Fascist Build Policy; Built Files not in SPEC
Product: Fedora
Classification: Fedora
Component: libuser (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Miloslav Trmač
Depends On:
  Show dependency treegraph
Reported: 2006-03-09 23:36 EST by Joseph D. Wagner
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 0.53.8-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-09 23:43:38 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Log of attempted build. (97.60 KB, text/plain)
2006-03-09 23:37 EST, Joseph D. Wagner
no flags Details

  None (edit)
Description Joseph D. Wagner 2006-03-09 23:36:26 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux 2.6.15-1.1833_FC4; X11; i686; en_US) KHTML/3.5.1 (like Gecko)

Description of problem:
To catch potential problems with SPEC files, rpmbuild checks if any files are 
in the %RPM_BUILD_ROOT directory that aren't listed in the %files section of 
the SPEC files (a.k.a. The Fascist Build Policy).  rpmbuild for this package 
fails at this check. 

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

How reproducible:

Steps to Reproduce:
Simply execute the following command on systems with rpm-build >= 4.4: 
rpmbuild --rebuild libuser-0.53.7-1.src.rpm 

Actual Results:  rpmbuild exited with error when it found files built that were not part of the 

Expected Results:  The package should have been built successfully. 

Additional info:

The Fascist Build Policy cannot be turned off from the command line.
Comment 1 Joseph D. Wagner 2006-03-09 23:37:03 EST
Created attachment 125926 [details]
Log of attempted build.
Comment 2 Miloslav Trmač 2006-03-09 23:43:38 EST
This is already fixed in rawhide (and soon to be released FC 5) since

Thanks for your report.

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