I have a series of RPM spec files and no debuginfo directive set in them. When I run rpmbuild, some packages generate a debuginfo rpm, some do not. What is the criteria used by rpm to decide if a debuginfo is generated? It seems to me that:

  • only arch packages generate debuginfo (noarch packages do not)
  • only main package in spec generates debuginfo (subpackages do not)

Someone can confirm if these rules are valid and if there are any others?

I have redhat-rpm-config installed, what is a prerequisite to generate debuginfo packages, according to https://fedoraproject.org/wiki/Packaging:Debuginfo?rd=Packaging/Debuginfo.

  • 1
    If what you're really wanting to know is 'why isn't my debug package being build', then you might also check for (wrongly) commented entries like the following: #%define debug_package 1 That looks like a comment, but is not quite. Struck me once; I wrote about it at distracted-it.blogspot.co.nz/2014/08/… – Cameron Kerr Apr 10 '15 at 11:20

%debug_package has to be included in .spec file. I used to write it before %prep stage. Also, __debug_package macro has to be 1.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.