-
Notifications
You must be signed in to change notification settings - Fork 352
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
Labels
Comments
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
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
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:
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.
The text was updated successfully, but these errors were encountered: