Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

It is currently not possible to completely disable rpm own debuginfo generation code #3057

Open
simo5 opened this issue Apr 23, 2024 · 0 comments · May be fixed by #3061
Open

It is currently not possible to completely disable rpm own debuginfo generation code #3057

simo5 opened this issue Apr 23, 2024 · 0 comments · May be fixed by #3061
Assignees
Labels

Comments

@simo5
Copy link

simo5 commented Apr 23, 2024

Describe the bug
I have spent some time trying to create a completely custom debuginfo file for a package I maintain.

Currently it is not possible to do so. Even disabling the custom package template and the whole debug_package machinery via %global debug_package %{nil} if rpm build see a package named %{name}-debuginfo it will always interfere with the build process of that package.

Namely the code will disregard any file list provide by either the %files section or via __find_debuginfo script and will instead process to reconstruct a new file list by searching for files named *-%{name}-%version}.%{release}.debug

To Reproduce
Steps to reproduce the behavior:

  1. Disable debug package creation
  2. Add an explicit %{name}-debuginfo package
  3. Try to include arbitrary files in it

Please link or attach the packages or spec files involved.

Expected behavior
When debug package creation is disabled the "main" debuginfo package file lists should not be tampered with.

Additional context
At the moment the only workaround I found was to create a fake subpackage and debuginfo subpackage and that allows me to include whatever content I need, but this is not a good solution.

@ffesti ffesti self-assigned this Apr 24, 2024
@ffesti ffesti added the bug label Apr 24, 2024
ffesti added a commit to ffesti/rpm that referenced this issue Apr 24, 2024
If the automatic creation of debuginfo packages is switched off via the
_enable_debug_packages macro don't touch debuginfo packages that are
declared in the spec file. If the packager created those on their own we
should not mess with them.

Resolves: rpm-software-management#3057
@ffesti ffesti linked a pull request Apr 24, 2024 that will close this issue
@simo5 simo5 changed the title I is currently not possible to completely disable rpm own debuginfo generation code It is currently not possible to completely disable rpm own debuginfo generation code Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

2 participants