Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eYhEu-00013g-UI for pgsql-pkg-yum@arkaria.postgresql.org; Mon, 08 Jan 2018 23:54:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eYhEt-0004Ka-TK for pgsql-pkg-yum@arkaria.postgresql.org; Mon, 08 Jan 2018 23:53:59 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eYhBh-0001Jz-Gd for pgsql-pkg-yum@lists.postgresql.org; Mon, 08 Jan 2018 23:50:41 +0000 Received: from mail-yb0-x232.google.com ([2607:f8b0:4002:c09::232]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eYhBc-0004z0-7g for pgsql-pkg-yum@lists.postgresql.org; Mon, 08 Jan 2018 23:50:39 +0000 Received: by mail-yb0-x232.google.com with SMTP id j7so5260050ybl.3 for ; Mon, 08 Jan 2018 15:50:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=citusdata.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Ul3YLXXaDbs1rgtWR8febvStG/D+7J9mvhOYpPUgrLM=; b=NcBCmYOoXF0ggnJMDzKH9cmoKbUuk/tv6VKhfLs4rjvR63dhO7Jp5nQIIM2qpJht6n rK8P0ApyIFYT4y3KO2dokjdY4/17erZ13co8uTLS+Yj57tGfOSr4lMBrBt3w4GJ0JhuB QtmkgcX1WQrp2vAf4VjVKLc8EzNDHMguj6p+0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Ul3YLXXaDbs1rgtWR8febvStG/D+7J9mvhOYpPUgrLM=; b=HKpk22iXE7Tng56Ij86wsgFJTDhLZbJ/iq354it9sgSqx0Q5Sc4fxTNXr6/ww8EF8J MiOsEnHtTbetRBNZEkiSX3O83lVFaV+4G/BdxRfpNfDEKfGs59AFEBWV3ln72Cqg/GjY 1N2nmTtvFIPB2ZCDmiM5Q3o5vyEX7KaUnJH4Uxo1eggPLPfBEfXRiOsykHZR2UBv6XIs OBkXrDLKLZM9+cLOLTZy4l8G6SXUXPHTjP4qwkZjB7ydGSYOt+HsSnyqd2+t8XKboYQw R1TRUAQjbv7T6A2j/jBSW/x1eugqDw3BXO866Uqv0XHVepYwa5w4hvfrUg3ozNU1Xjai uMdg== X-Gm-Message-State: AKGB3mIRg++tX51IFQBv+Pb9mpb7+r0WSrl1jAYJyoIYcRLmiIMarH97 pvrEfBYSpwxukbLzp5R5EyuOIbcBdUBwtOspb7TywA== X-Google-Smtp-Source: ACJfBotmkTgMkdHQCSOLzQKSNI9/sUDIyb6KK0/FWjFZo350fCO1FontT+AD+wg62whh+NM48svKHajojFuMeodAEqQ= X-Received: by 10.37.164.35 with SMTP id f32mr12385406ybi.5.1515455434889; Mon, 08 Jan 2018 15:50:34 -0800 (PST) MIME-Version: 1.0 References: <3121414.gbAxY14dXi@nb.usersys.redhat.com> In-Reply-To: <3121414.gbAxY14dXi@nb.usersys.redhat.com> From: Daniel Farina Date: Mon, 08 Jan 2018 23:50:24 +0000 Message-ID: Subject: Re: How are debuginfo packages generated? To: Pavel Raiskup Cc: pgsql-pkg-yum@lists.postgresql.org, Craig Ringer , pgsql-pkg-yum Content-Type: multipart/alternative; boundary="94eb2c1462f4ded45405624c7661" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --94eb2c1462f4ded45405624c7661 Content-Type: text/plain; charset="UTF-8" On Fri, Jan 5, 2018 at 10:48 PM Pavel Raiskup wrote: > On Saturday, January 6, 2018 6:52:12 AM CET Daniel Farina wrote: > > On Fri, Jan 5, 2018 at 9:50 PM Craig Ringer > wrote: > > > > > On 6 January 2018 at 06:30, Daniel Farina > 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): > Seems to me _enable_debug_packages is not "1" on Amazon Linux, nor is that hook in in /usr/lib/rpm/redhat/macros, though that can be from simple divergence of sorts. I also have a Fedora 27 to compare to. I wonder how the PGDG repository did this on the older Amazon Linux it supported? Did it? I'll bark up that tree for a while. Thanks. --94eb2c1462f4ded45405624c7661 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Jan 5,= 2018 at 10:48 PM Pavel Raiskup <praiskup@redhat.com> wrote:
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:<= br> > >
> >> Hello,
> >>
> >> For quite some time, I've been building lightly modified = PGDG packages,
> >> but I have never figured how PGDG's yum repo gets debugin= fo packages. When
> >> I have built them, unless I hack up the spec file to have &qu= ot;%debug_package"
> >> I do not get such a debuginfo package. Clearly, that is not h= ow 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 whe= re
you build the package because debuginfo generator is tightly dependant on the _setup_ in packages like 'rpm', 'redhat-rpm-config', et= c.

Have a look at `rpm --eval %debug_package` output to see what happens
there, and to see why it is needed.=C2=A0 Then, study your system/user rpm = macros.
On my system (Fedora 27 x86_64), there's is (in /usr/lib/rpm/redhat/mac= ros):
=C2=A0
Seems to me _enable_debug_packages is not "1" on Am= azon Linux, nor is that hook in in /usr/lib/rpm/redhat/macros, though that = can be from simple divergence of sorts. I also have a Fedora 27 to compare = to. I wonder how the PGDG repository did this on the older Amazon Linux it = supported? Did it?

I'll bark up that tree for a while. Thanks.
--94eb2c1462f4ded45405624c7661--