Re: How are debuginfo packages generated?

On Saturday, January 6, 2018 6:52:12 AM CET Daniel Farina wrote:
> On Fri, Jan 5, 2018 at 9:50 PM Craig Ringer <craig@2ndquadrant.com> wrote:
> 
> > On 6 January 2018 at 06:30, Daniel Farina <daniel@citusdata.com> wrote:
> >
> >> Hello,
> >>
> >> For quite some time, I've been building lightly modified PGDG packages,
> >> but I have never figured how PGDG's yum repo gets debuginfo packages. When
> >> I have built them, unless I hack up the spec file to have "%debug_package"
> >> I do not get such a debuginfo package. Clearly, that is not how the spec
> >> files work as-is in pgrpms.
> >>
> >
> > How do you invoke rpmbuild?
> >
> 
> Via make nopreprpm10.

I've never heard about nopreprpm10, but it is more important to say where
you build the package because debuginfo generator is tightly dependant on
the _setup_ in packages like 'rpm', 'redhat-rpm-config', etc.

Have a look at `rpm --eval %debug_package` output to see what happens
there, and to see why it is needed.  Then, study your system/user rpm macros.
On my system (Fedora 27 x86_64), there's is (in /usr/lib/rpm/redhat/macros):

  ...
  %install %{?_enable_debug_packages:%{?buildsubdir:%{debug_package}}}\
  %%install\
  %{nil}
  ...

. so the %debug_package content is automatically hooked right before
%install by default, but only if %_enable_debug_packages is defined (the
default though).  Then, you need to have all the stuff done correctly in
%__debug_install_post (namely /usr/lib/rpm/find-debuginfo.sh should be
%called) but this appears to be OK on your system.

Pavel