Bug 1476593 - rpm: python3 build failure related to debuginfo extraction
rpm: python3 build failure related to debuginfo extraction
Status: NEW
Product: Fedora
Classification: Fedora
Component: rpm (Show other bugs)
27
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: packaging-team-maint
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-30 11:10 EDT by Florian Weimer
Modified: 2017-08-15 04:41 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Florian Weimer 2017-07-30 11:10:11 EDT
I have encountered a build failure due to debuginfo extraction:

  https://koji.fedoraproject.org/koji/taskinfo?taskID=20903200

Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/python3-3.6.2-3.fc27.s390x
RPM build errors:
error: Installed (but unpackaged) file(s) found:
   /usr/lib/debug/usr/lib64/__pycache__/libpython3.6dm.so.1.0.debug-gdb.cpython-36.opt-1.pyc
   /usr/lib/debug/usr/lib64/__pycache__/libpython3.6dm.so.1.0.debug-gdb.cpython-36.opt-2.pyc
   /usr/lib/debug/usr/lib64/__pycache__/libpython3.6dm.so.1.0.debug-gdb.cpython-36.pyc
   /usr/lib/debug/usr/lib64/__pycache__/libpython3.6m.so.1.0.debug-gdb.cpython-36.opt-1.pyc
   /usr/lib/debug/usr/lib64/__pycache__/libpython3.6m.so.1.0.debug-gdb.cpython-36.opt-2.pyc
   /usr/lib/debug/usr/lib64/__pycache__/libpython3.6m.so.1.0.debug-gdb.cpython-36.pyc
   /usr/lib/debug/usr/lib64/libpython3.6dm.so.1.0.debug-gdb.py
   /usr/lib/debug/usr/lib64/libpython3.6m.so.1.0.debug-gdb.py
    Duplicate build-ids /builddir/build/BUILDROOT/python3-3.6.2-3.fc27.s390x/usr/bin/python3.6 and /builddir/build/BUILDROOT/python3-3.6.2-3.fc27.s390x/usr/libexec/system-python
    File listed twice: /usr/lib/.build-id/94/cd86a8356e4dd936e193186805048cbee6e07e
    File listed twice: /usr/lib64/libpython3.6dm.so.1.0
    Duplicate build-ids /builddir/build/BUILDROOT/python3-3.6.2-3.fc27.s390x/usr/lib/debug/usr/bin/python3.6-3.6.2-3.fc27.s390x.debug and /builddir/build/BUILDROOT/python3-3.6.2-3.fc27.s390x/usr/lib/debug/usr/libexec/system-python-3.6.2-3.fc27.s390x.debug
    Installed (but unpackaged) file(s) found:
   /usr/lib/debug/usr/lib64/__pycache__/libpython3.6dm.so.1.0.debug-gdb.cpython-36.opt-1.pyc
   /usr/lib/debug/usr/lib64/__pycache__/libpython3.6dm.so.1.0.debug-gdb.cpython-36.opt-2.pyc
   /usr/lib/debug/usr/lib64/__pycache__/libpython3.6dm.so.1.0.debug-gdb.cpython-36.pyc
   /usr/lib/debug/usr/lib64/__pycache__/libpython3.6m.so.1.0.debug-gdb.cpython-36.opt-1.pyc
   /usr/lib/debug/usr/lib64/__pycache__/libpython3.6m.so.1.0.debug-gdb.cpython-36.opt-2.pyc
   /usr/lib/debug/usr/lib64/__pycache__/libpython3.6m.so.1.0.debug-gdb.cpython-36.pyc
   /usr/lib/debug/usr/lib64/libpython3.6dm.so.1.0.debug-gdb.py
   /usr/lib/debug/usr/lib64/libpython3.6m.so.1.0.debug-gdb.py
Child return code was: 1

This happened with rpm-build 4.13.0.1-40.fc27.
Comment 1 Mark Wielaard 2017-08-01 08:45:57 EDT
This is caused by split debuginfo checking which file corresponds to
which main/sub-package. Without split debuginfo anything found
under /usr/lib/debug is just put into the -debuginfo package, no
questions asked.

The immediate workaround is to add the following to your spec file:
%undefine _debuginfo_subpackages
(Which is what was done for python3-3.6.2-4.fc27)

This disables split debuginfo packages and just generates one big
-debuginfo packages with everything under /usr/lib/debug/ included.

But this might or might not be a packaging bug. In particular if it
contains generated pyc files those probably really shouldn't be there.

The basic issue is that we have been trying to make the debuginfo
packages self-contained and non-conflicting between versions.
So you can easily install debuginfo for different (bi)arches or
versions. But some packages assume that if they drop anything
under /usr/lib/debug it will just magically appear in the debuginfo
package (which has been historically true). But with the split
debuginfo we have to make a choice which subpackage it belongs
to. One possible rpm fix would probably be to add such files to the
"main" debuginfo package.

But it would probably be better to move these files to the
python3-devel package. Maybe we should discuss with the gdb
maintainers how/where they would like to see these gdb python
extensions installed. I doubt the -debuginfo package really is
the place for them anyway.
Comment 3 Jan Kurik 2017-08-15 04:41:46 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

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