Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eXhPA-0008PP-O0 for pgsql-pkg-yum@arkaria.postgresql.org; Sat, 06 Jan 2018 05:52:28 +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 1eXhPA-0007Cv-B0 for pgsql-pkg-yum@arkaria.postgresql.org; Sat, 06 Jan 2018 05:52:28 +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 1eXhPA-0007Cl-61 for pgsql-pkg-yum@lists.postgresql.org; Sat, 06 Jan 2018 05:52:28 +0000 Received: from mail-yw0-x22f.google.com ([2607:f8b0:4002:c05::22f]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eXhP7-0006P1-5k for pgsql-pkg-yum@postgresql.org; Sat, 06 Jan 2018 05:52:27 +0000 Received: by mail-yw0-x22f.google.com with SMTP id z132so2545575ywd.9 for ; Fri, 05 Jan 2018 21:52:24 -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=kuufKYdf6RAo73/H8cou8939jlDKT9/H5Id1V1FPyjg=; b=LU3qlqoXCZYMTBJBq+cngB0qcNoVzUJgzWqHT+daTUxOND1pTkQnKwIx7NlA6F+zuw WP/93pLp7JddM1Ht/WNfM3hptpUw86NlXBaXVEMUPGHIordlHnK0Oa0R3OF7mY+MEywN toU8HMrgN6h3HV72fefTWsW7R9GiNJ8AkYaWY= 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=kuufKYdf6RAo73/H8cou8939jlDKT9/H5Id1V1FPyjg=; b=eZRtsVps8SV8JpSTSi0dupoQ2oSD/Vtkd8e7+YbpyEYoZxyaAP/S2zdAIi3Cqw8IQR u0CvOuqGqlq6zlRU99VLxaXKPVqdgmHTLX3ydBO3wY60zSPxkCxdU2MKlDJO45s6Hz0w 8yc3M6ia+oJADz+IHat15fua5qYoz+LxlBAtZOPkGcLwRM62nPxxzYdjEt2pzJFzdpbd 8IxScmcnPw0+R+g/aDTweAwAbun8EIqBmSsb5dbGZ6VhkzFHnyMNpRvQ1v4ghypDe0cF nMDFxLbaNe8d7Cy26gM59/JwaEaZSsAlUo6Txk8qsKIUUSjB3xWB2zjJmOrUNXoOFp+9 R7yw== X-Gm-Message-State: AKGB3mJa3AsABXM14NxDTFcQLip9vJxE2sAGtuqRC449aYtBmwwPIrgN ALExuypumseMEDzdoeKIqfD8qop0OaXLPRPdjWxN3g== X-Google-Smtp-Source: ACJfBouPP2Mf9NKofqCWFrvjIvFBTa8RGb9wsvnQC28UbllHQqUmvBuOtc77CFXhZSeqjJfw7394/bK7HRYRSSSt0BU= X-Received: by 10.129.174.35 with SMTP id m35mr4924032ywh.196.1515217943127; Fri, 05 Jan 2018 21:52:23 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Daniel Farina Date: Sat, 06 Jan 2018 05:52:12 +0000 Message-ID: Subject: Re: How are debuginfo packages generated? To: Craig Ringer Cc: pgsql-pkg-yum Content-Type: multipart/alternative; boundary="f403045e89c04200d60562152b01" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --f403045e89c04200d60562152b01 Content-Type: text/plain; charset="UTF-8" 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. --f403045e89c04200d60562152b01 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Jan 5, 2018 at 9:5= 0 PM Craig Ringer <craig@2ndqua= drant.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 su= ch a debuginfo package. Clearly, that is not how the spec files work as-is = in pgrpms.

How do you invoke = rpmbuild?

<= div dir=3D"auto">Via make nopreprpm10. --f403045e89c04200d60562152b01--