Bug 127227 - Segv. when building an RPM with an empty .fc file
Summary: Segv. when building an RPM with an empty .fc file
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: rawhide
Hardware: powerpc
OS: Linux
medium
high
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-07-04 21:36 UTC by W. Michael Petullo
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-07-04 21:50:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description W. Michael Petullo 2004-07-04 21:36:46 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.6)
Gecko/20040510 Epiphany/1.2.4

Description of problem:
The rpm command consistently crashes with a segv. when building a
package that contains an empty SELinux file context definition file. 
For example, if the specification file contains:

%policy
%{_sysconfdir}/selinux/strict/src/policy/file_contexts/misc/pam_keyring.fc

and pam_keyring.fc is an empty file then the rpmbuild process will die:

[...]
+ install --owner=root --group=root --mode=0644
config/pam_keyring_macros.te
/tmp/pam_keyring-0.0.2-0.fdr.1-root-mike//etc/selinux/strict/src/policy/macros
+ install --owner=root --group=root --mode=0644 config/pam_keyring.fc
/tmp/pam_keyring-0.0.2-0.fdr.1-root-mike//etc/selinux/strict/src/policy/file_contexts/miscProcessing
files: pam_keyring-0.0.2-0.fdr.1
make: *** [rpm] Error 139

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

How reproducible:
Always

Steps to Reproduce:
See above.  I can provide a tarball and RPM specification that causes
this crash if needed.
    

Additional info:

Comment 1 Jeff Johnson 2004-07-04 21:47:12 UTC
"Don't do that." is the only answer I got atm.


Comment 2 Jeff Johnson 2004-07-04 21:50:10 UTC
In fact, %policy is headed out of rpmbuild and *.spec files
entirely. There is no reason to attempt adding %policy
any more at all.

WONTFIX, in the sense that s/%policy// is no fix at all.


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