Bug 83295 - rpmbuild doesn't follow macros for unpackaged files
Summary: rpmbuild doesn't follow macros for unpackaged files
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: rpm-build
Version: 1.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-02-01 20:11 UTC by sean
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-02-01 20:19:59 UTC


Attachments (Terms of Use)

Description sean 2003-02-01 20:11:11 UTC
Description of problem:
I'm getting an unpackaged files problem in trying to build wine from a source rpm:

Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/wine-root
error: Installed (but unpackaged) file(s) found:
   /usr/share/aclocal/wine.m4
 
 
RPM build errors:
    Installed (but unpackaged) file(s) found:
   /usr/share/aclocal/wine.m4

and it dies.

/etc/rpm/macros has :

 cat /etc/rpm/macros
%optflags   -O2 -march=athlon-xp -m3dnow -msse
%define _unpackaged_files_terminate_build 0

I even went into /usr/lib/rpm/macros:

#
# Should unpackaged files in a build root terminate a build?
#
# Note: The default value should be 0 for legacy compatibility.
%_unpackaged_files_terminate_build	0

#
# Should missing %doc files in the build directory terminate a build?
#
# Note: The default value should be 0 for legacy compatibility.
%_missing_doc_files_terminate_build	0

#

What am I missing?

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

rpm -q rpm-build
rpm-build-4.2-0.64

How reproducible:


Steps to Reproduce:
1.
2.
3.
    
Actual results:


Expected results:


Additional info:

Comment 1 Jeff Johnson 2003-02-01 20:19:59 UTC
Yo need to delete the "%define", copy what's in
/usr/lib/rpm/macros changing 1 to 0.

Comment 2 sean 2003-02-01 23:11:45 UTC
Yep. It turned out deleting the %define was half the problem. You need a tab -
not a space - before the 0 ( or 1).

thanks for the quick response.


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