riscv/planning
11
1
Fork 0
Code Issues 21 Pull requests Projects Releases Packages Wiki Activity Actions

Some packages fail due to "Empty %files file /builddir/build/BUILD/***/debugsourcefiles.list" error #13

New issue
Open
opened 2026-03-17 10:51:05 +00:00 by hrw · 4 comments
hrw commented 2026-03-17 10:51:05 +00:00
Owner
Copy link

We passed serious debugedit problem and now we have one more to solve. There are packages which fail because their build generates empty "debugsourcefiles.list" file.

Examples:

  • catch
  • opensurge
  • pam-u2f
  • pgadmin4
  • python-ssh-python
  • surgescript
  • toolbox
We passed serious debugedit problem and now we have one more to solve. There are packages which fail because their build generates empty "debugsourcefiles.list" file. Examples: - catch - opensurge - pam-u2f - pgadmin4 - python-ssh-python - surgescript - toolbox
davidlt commented 2026-03-17 11:18:00 +00:00
Owner
Copy link

We have discussed this before on the Matrix channel, and I did some debugging. The issue is understood (see debugedit ticket: https://sourceware.org/bugzilla/show_bug.cgi?id=33823 ). Basically this due to relative paths being used in DWARF debug information and thus debugedit cannot handle those. Debugedit needs to replace basedir (which incl. built time path) with a new basedir that would match install location. Relative paths don't allow that.

Note, that this might become a bigger issue as this is what reproducible builds suggests to do. For example, toolbox.

We have discussed this before on the Matrix channel, and I did some debugging. The issue is understood (see debugedit ticket: https://sourceware.org/bugzilla/show_bug.cgi?id=33823 ). Basically this due to relative paths being used in DWARF debug information and thus debugedit cannot handle those. Debugedit needs to replace basedir (which incl. built time path) with a new basedir that would match install location. Relative paths don't allow that. Note, that this might become a bigger issue as this is what reproducible builds suggests to do. For example, toolbox.
davidlt commented 2026-03-17 11:19:01 +00:00
Owner
Copy link

Another comment. This is broken all arches, not riscv64 specific. On all other arches debugedit returns an empty directory which gets packages, but on riscv64 it returns nothing and it fails.

Another comment. This is broken all arches, not riscv64 specific. On all other arches debugedit returns an empty directory which gets packages, but on riscv64 it returns nothing and it fails.
yaneti commented 2026-03-17 19:21:32 +00:00
Copy link

Something similar to this https://src.fedoraproject.org/rpms/pam-u2f/pull-request/3 for pam-u2f could be a temporary workaround for the affected packages

Something similar to this https://src.fedoraproject.org/rpms/pam-u2f/pull-request/3 for pam-u2f could be a temporary workaround for the affected packages
hrw commented 2026-07-09 14:57:07 +00:00
Author
Owner
Copy link

We have those listed in the tracker:

  • catch
  • opensurge
  • pgadmin4
  • python-dbus-fast
  • python-zeroconf
  • surgescript
  • toolbox

Of those, when it comes to Fedora 45, pgadmin4 misses some deps and the rest still have that problem.

We have those listed in the tracker: - catch - opensurge - pgadmin4 - python-dbus-fast - python-zeroconf - surgescript - toolbox Of those, when it comes to Fedora 45, `pgadmin4` misses some deps and the rest still have that problem.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
riscv/planning#13
No description provided.