Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eXhNl-0008Jy-7g for pgsql-pkg-yum@arkaria.postgresql.org; Sat, 06 Jan 2018 05:51: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 1eXhNj-00074M-TA for pgsql-pkg-yum@arkaria.postgresql.org; Sat, 06 Jan 2018 05:50:59 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eXhNj-00074C-K2 for pgsql-pkg-yum@lists.postgresql.org; Sat, 06 Jan 2018 05:50:59 +0000 Received: from mail-ua0-x242.google.com ([2607:f8b0:400c:c08::242]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eXhNb-0006OX-Lk for pgsql-pkg-yum@postgresql.org; Sat, 06 Jan 2018 05:50:58 +0000 Received: by mail-ua0-x242.google.com with SMTP id r18so3827072uak.4 for ; Fri, 05 Jan 2018 21:50:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hfLokT2j35kBKWD2ex7VXbZv5ejkNrKtEkVoZ4D94aU=; b=vGw1vafsgrY+W0BcpYZ4emLyVipf0ziP9sB6fGb3PFSfDh2iomh3SOVuQy3BZIlCLp WtjicVnzlTEcHjD1Wkr8GHc0PsEaw519V8cPKGt8+Ymh/fSfvluJl2waxtaGurOVwDGp UwyGYhbHvn6dnAW1+irXr8idoQWtzhcL7wcl4R6rfffPca5mV1UNr+NV0UJpGOneDnsx Ia5TMfcDTnk38l0PaZQpzDAQTI4g/2LMvfxYRu8ndbBq5mUkWGCHDex5GSfwq2LfBj3i 8zlY8jhZK3rJ5kjeF1H/X2axlMQ1bVOXxWDooP2g8KYiEzqysQWzgXjEYBjOrQluYO59 WEew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hfLokT2j35kBKWD2ex7VXbZv5ejkNrKtEkVoZ4D94aU=; b=iijuLkbeZu08LCfqosnxxRQCT7NX5sDB5BU/H8s9M0qF/oFTbTw38o7p6D0rTWGvMr +2/KpucLi31mqw+pWOepI8F4lAd8v3J8QA73AN4K0FnP/jUzoeCJlt0SK2ReG2pLuDzG 08xiQl1B67vuIWzz9j4H7Ul8TceGPda6IN5jmPhZj6KNs9RtnUEF+uU0yQppn47IEYNR GGkPfMlck7+FwqipdwFMqRiLmIRTI/m357tI/Ib0bf6KlUZRYEVZpooUH/7aZEqugQ9z UGnKcpmHZtj00AIRsLKlx5yroB9/rUnXlwXmppMsTbBssHOnKxqu7B+Iifnb1OqNkeU+ I+wg== X-Gm-Message-State: AKGB3mJTsQUK+8Lo0JJvGCuKT6hknjMdtDsN1sVEUwDw3R37AoJ3mb/f EEjq5mRQbBRjLoOZ5NGbnX3snvrOCwTu7PzOfB/6iQ== X-Google-Smtp-Source: ACJfBouWhUX/lFdEr8IjuusZrDRS1cyQP9rUp8Xv1hp68SBkegz9/n4xtIllSozkylJM54MPEJmqHVdgJB62PSUYtIs= X-Received: by 10.159.50.50 with SMTP id x47mr5189969uad.139.1515217848739; Fri, 05 Jan 2018 21:50:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.73.235 with HTTP; Fri, 5 Jan 2018 21:50:48 -0800 (PST) In-Reply-To: References: From: Craig Ringer Date: Sat, 6 Jan 2018 13:50:48 +0800 Message-ID: Subject: Re: How are debuginfo packages generated? To: Daniel Farina Cc: pgsql-pkg-yum Content-Type: multipart/alternative; boundary="001a1147645ea1df8c0562152566" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --001a1147645ea1df8c0562152566 Content-Type: text/plain; charset="UTF-8" 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? I get debuginfo packages. I build srpms then rpmbuild --rebuild them. Usually using mock, though moving toward docker these days so I can use the same toolchain for my debian build pipeline too. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services --001a1147645ea1df8c0562152566 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On 6= January 2018 at 06:30, Daniel Farina <daniel@citusdata.com> wrote:
Hello,
For quite some time, I've been building lightly modified P= GDG 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= "%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?

I get debuginfo packages. I build srpms then rpmbuild --rebuild them. Usua= lly using mock, though moving toward docker these days so I can use the sam= e toolchain for my debian build pipeline too.

-- =
=C2=A0Craig Ringer=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 http= ://www.2ndQuadrant.com/
=C2=A0PostgreSQL Development, 24x7 Support, = Training & Services
--001a1147645ea1df8c0562152566--