Bug 1583329 - rpmbuild: Empty %files file debugsourcefiles.list
Summary: rpmbuild: Empty %files file debugsourcefiles.list
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-28 17:57 UTC by Miroslav Suchý
Modified: 2018-05-30 08:55 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-30 08:20:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Miroslav Suchý 2018-05-28 17:57:14 UTC
Description of problem:
I am getting from and rpmbuild:

Processing files: cello-debugsource-1.0-1.fc28.x86_64
error: Empty %files file /home/christian/rpmbuild/BUILD/cello-1.0/debugsourcefiles.list

For more info and files for reproducer see
https://github.com/redhat-developer/rpm-packaging-guide/issues/47

I tried and reproduced this on recent Fedora28.

Version-Release number of selected component (if applicable):
rpm-build-4.14.1-9.fc28.x86_64

How reproducible:
always

Steps to Reproduce:
1. build package cello.src.rpm as documented in packaging guide
2. try to rebuild it (to get a binary package).

Comment 1 Mark Wielaard 2018-05-28 18:47:17 UTC
You are not building any debuginfo:

gcc -o cello cello.c

Try the following:

gcc -g -o cello cello.c

Otherwise it will be impossible for rpmbuild to determine the debug source files and debuginfo files to package.

Comment 2 Miroslav Suchý 2018-05-30 08:20:55 UTC
Indeed. I will fix the guide. Thank you.

Comment 3 Panu Matilainen 2018-05-30 08:36:15 UTC
Just makes me wonder if we couldn't do a better job at reporting the *actual* problem especially now that much of the build-id extraction occurs inside rpmbuild code...

Comment 4 Mark Wielaard 2018-05-30 08:55:15 UTC
(In reply to Panu Matilainen from comment #3)
> Just makes me wonder if we couldn't do a better job at reporting the
> *actual* problem especially now that much of the build-id extraction occurs
> inside rpmbuild code...

The build-ids match executable builds and debuginfo files, the builds would still have build-ids. This particlar error occurs earlier because no source files can be found at all.

There is however a test in find-debuginfo.sh that checks for case:

if [ -s "$SOURCEFILE" ]; then
...
fi

We might want to add an else with a warning there?


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