Bug 505658 - [Stratus 5.6 bug] rpmbuild fails reporting unpackaged .pyo and .pyc files
[Stratus 5.6 bug] rpmbuild fails reporting unpackaged .pyo and .pyc files
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: rpm (Show other bugs)
All Linux
medium Severity medium
: alpha
: 5.6
Assigned To: Panu Matilainen
BaseOS QE Security Team
: OtherQA
Depends On:
Blocks: 557597
  Show dependency treegraph
Reported: 2009-06-12 15:21 EDT by Rich Johnson
Modified: 2011-03-15 09:53 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-30 13:24:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rich Johnson 2009-06-12 15:21:51 EDT
Description of problem:
Occasional failure packaging python files.
I suspect brp-python-bytecompile.  This also may be related to bug 468179

The symptom is not 100% reproducible. 

Version-Release number of selected component (if applicable):
-bash-3.2$ rpmbuild --version
RPM version

How reproducible:
Create an architecture specific rpm delivering at least one python file.
rpmbuild.  In this case it is the file /usr/lib/yum-plugins/ft-reboot-tracking.py.

Steps to Reproduce:
Actual results:

buildrpm reports: 

Checking for unpackaged file(s): /usr/lib/rpm/check-files /auto/svn/rjohnson/linux/trunk/ftl_linux/build/BUILDROOT/lsb-ft-cstools-7.0.3-104
error: Installed (but unpackaged) file(s) found:

RPM build errors:
    Installed (but unpackaged) file(s) found:

Expected results:

Since the offending files were created during %__os_install_post processing
The expected  behavior is that any files created by rpmbuild's macros are either:
a)  added to the %files set for management by rpm 
b)  ignored during packaging

Any notice of the additional files should be informational only.  It should not raise an error. 

Additional info:
The lack of 100% repeatability is pernicious because if one adds the .pyc and .pyo files a subsequent rpmbuild may fail to create them and then fail complaining that that specified files are missing.

One avoidance is to recast the __os_install_post macro; skipping brp_python_bytecompile

%define __os_install_post     /usr/lib/rpm/redhat/brp-compress
    %{!?__debug_package:/usr/lib/rpm/redhat/brp-strip %{__strip}}
    /usr/lib/rpm/redhat/brp-strip-static-archive %{__strip}
    /usr/lib/rpm/redhat/brp-strip-comment-note %{__strip} %{__objdump}
Comment 1 Rich Johnson 2009-06-12 15:31:31 EDT
Probably not relevant, but the symptom arose creating a sub-package for an x86_64 package.
Comment 2 Andrius Benokraitis 2009-06-23 00:32:49 EDT
Proposing for RHEL 5.5, unless there is an extenuating business case for this to be proposed for RHEL 5.4 by Stratus.
Comment 3 Nate Straz 2009-09-30 16:25:03 EDT
Related to bug 236535
Comment 4 Chris Ward 2009-10-13 11:05:11 EDT

We would like to confirm that there is commitment to test 
for the resolution of this request during the RHEL 5.5 test
phase, if it is accepted into the release. 

Please post a confirmation before Oct 16th, 2009, 
including the contact information for testing engineers.
Comment 5 Rich Johnson 2009-10-14 07:45:55 EDT
I am signed up to test from the Stratus side.
Comment 6 RHEL Product and Program Management 2009-11-06 14:13:01 EST
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
Comment 7 Andrius Benokraitis 2009-11-10 12:55:22 EST
Deferring to RHEL 5.6 with OK from Stratus.
Comment 9 Andrius Benokraitis 2010-07-30 11:06:24 EDT
Rich @ Stratus: I'm getting word that this probably won't ever get fixed in RHEL 5. What's your take on this?
Comment 10 Rich Johnson 2010-07-30 12:56:43 EDT
(In reply to comment #9)
> Rich @ Stratus: I'm getting word that this probably won't ever get fixed in
> RHEL 5. What's your take on this?    

Not getting a fix in RHEL 5 is fine.  We have a workaround.

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