public inbox for [email protected]
help / color / mirror / Atom feedFrom: Daniel Farina <[email protected]>
To: Craig Ringer <[email protected]>
Cc: pgsql-pkg-yum <[email protected]>
Subject: Re: How are debuginfo packages generated?
Date: Sat, 06 Jan 2018 05:52:12 +0000
Message-ID: <CAOPfGFiGgbJVv493Di-3cHHsUOODo3KTW+grSOdT0JjVfsa5LQ@mail.gmail.com> (raw)
In-Reply-To: <CAMsr+YEEB1C9ir4CBMh2YcFBS5zJf3bcWxPwNkF7VZjmMsJvTQ@mail.gmail.com>
References: <CAOPfGFjKGSjo5MSURH0UGtLHzzZ_7_rwaS=JGETHFMrKxGpE8g@mail.gmail.com>
<CAMsr+YEEB1C9ir4CBMh2YcFBS5zJf3bcWxPwNkF7VZjmMsJvTQ@mail.gmail.com>
On Fri, Jan 5, 2018 at 9:50 PM Craig Ringer <[email protected]> wrote:
> On 6 January 2018 at 06:30, Daniel Farina <[email protected]> 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.
view thread (7+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: How are debuginfo packages generated?
In-Reply-To: <CAOPfGFiGgbJVv493Di-3cHHsUOODo3KTW+grSOdT0JjVfsa5LQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox