Bug 672879

Summary: rpmbuild with --nodirtokens creates empty package
Product: Red Hat Enterprise Linux 5 Reporter: Peter Åstrand <astrand>
Component: rpmAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED NEXTRELEASE QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.6CC: ffesti
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-11 14:17:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
minimal spec file none

Description Peter Åstrand 2011-01-26 16:23:56 UTC
Quoting from Bug 546663: --nodirtokens just refuses to stay fixed. Or with other words: This is a continuation of Bug 56040, Bug 462391, and Bug 546663. Those were Fedora bugs, but apparently the bug has found its way into RHEL 5 as well. 

Version information:

rpm-4.4.2.3-22.el5
rpm-python-4.4.2.3-22.el5
rpm-devel-4.4.2.3-22.el5
rpm-libs-4.4.2.3-22.el5
rpm-build-4.4.2.3-22.el5
rpmlint-0.91-1.el5
rpm-devel-4.4.2.3-22.el5
rpm-libs-4.4.2.3-22.el5

Comment 1 Peter Åstrand 2011-01-26 16:25:35 UTC
Created attachment 475432 [details]
minimal spec file

Example package / test case. Build with:

rpmbuild -ba minimal.spec

and

rpmbuild --nodirtokens -ba minimal.spec

Comment 2 Peter Åstrand 2011-01-26 16:31:16 UTC
I executed:

# yum downgrade rpm rpm-python rpm-devel rpm-libs rpm-build popt

This downgraded RPM to:

rpm-devel-4.4.2.3-20.el5_5.1
rpm-build-4.4.2.3-20.el5_5.1
rpm-libs-4.4.2.3-20.el5_5.1
rpm-libs-4.4.2.3-20.el5_5.1
rpm-python-4.4.2.3-20.el5_5.1
rpm-devel-4.4.2.3-20.el5_5.1
rpm-4.4.2.3-20.el5_5.1

Problem remains.

Comment 3 Peter Åstrand 2011-01-27 08:33:38 UTC
This is the necessary patch:

http://rpm.org/gitweb?p=rpm.git;a=commit;h=7739cb6fffb2371266371ec58486a3cde4fca155

Since it's one the 4.4.x branch, it should be safe to include.

Comment 4 Florian Festi 2013-03-11 14:17:19 UTC
RHEL5 is now in the development phase 2. This limits updates to critical issues only. While this issue might be annoying it is now too late to get it fixed. Sorry.