Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-pkg-yum-owner+archive@lists.postgresql.org>)
	id 1eXaWA-0002xV-31
	for pgsql-pkg-yum@arkaria.postgresql.org; Fri, 05 Jan 2018 22:31:14 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-pkg-yum-owner+archive@lists.postgresql.org>)
	id 1eXaW9-0001UM-15
	for pgsql-pkg-yum@arkaria.postgresql.org; Fri, 05 Jan 2018 22:31:13 +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 <daniel@citusdata.com>)
	id 1eXaW8-0001UC-S7
	for pgsql-pkg-yum@lists.postgresql.org; Fri, 05 Jan 2018 22:31:12 +0000
Received: from mail-yw0-x229.google.com ([2607:f8b0:4002:c05::229])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <daniel@citusdata.com>)
	id 1eXaW6-0005TA-L1
	for pgsql-pkg-yum@postgresql.org; Fri, 05 Jan 2018 22:31:12 +0000
Received: by mail-yw0-x229.google.com with SMTP id u142so122691ywg.0
        for <pgsql-pkg-yum@postgresql.org>;
 Fri, 05 Jan 2018 14:31:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=citusdata.com; s=google;
        h=mime-version:from:date:message-id:subject:to;
        bh=TxcXEFfXuo+dsDftN8ITPUMAomulxzZldUlGhrykmFQ=;
        b=Nzo+1GXEhhncl1Pfef8vLliE/nO3AfvOjFY5hvNHVg0gC/dKeD3PotX4ZN3Q2pr6hq
         I5pAdZYXO2gDC/6S9fkSyybAWBL4cw7/0WtdIyp7lIoLBhnv/gyDoR+L+l8lVUNxUbsk
         LNwr2r4uxLHaTyp2Iov79S0fqaTy8SuhITLGw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
        bh=TxcXEFfXuo+dsDftN8ITPUMAomulxzZldUlGhrykmFQ=;
        b=FRrb58hkGvuLpKriuyjR4ADsD66nAM+IJcedR4UBDvI9uuN1DcNQvDzciQQ8rMFtXK
         NtzPEEsNND0ftbF/XFta7ybiAoGWIOuibdLw5gMajh47tn2N5tnehV+9QWf63/s3f7PC
         YXy1pnZ4vLgEaoc7iTXk94+k+1JhNFwm5fON70TGY8dg+1Za4s76W2+lztycKe2kwHbj
         zXMAR6xV480mEjdFwfzuFFWKjRTLWFP4tRJAfgKzHjAMRznFzsdVF795yz4X5BF9ylY/
         jI0OqWTJOZbeBroi3m3D1MwB11mKfodcpNLePEdJH3or5j8+P9zYPXH9VW9N2YLMWzSr
         P/WQ==
X-Gm-Message-State: AKGB3mKMpZDwouhB8ykcai1u95BaqjUs4Ph4iRQFXs5cRIEs2yqJ7ba0
	9dz0NEGgmkInMBJuXZG2d4zxBGVSYphnkI3fUsxoOuqr
X-Google-Smtp-Source: 
 ACJfBovmFFbgE+AswRqFYpRBYvzp+2mxcc2BZXykivaX/nRSn4sGJ4dkwlgRmHoVd+9nmo4upkyGdaf72oQ7rZWsz4E=
X-Received: by 10.129.174.35 with SMTP id m35mr4148026ywh.196.1515191467476;
 Fri, 05 Jan 2018 14:31:07 -0800 (PST)
MIME-Version: 1.0
From: Daniel Farina <daniel@citusdata.com>
Date: Fri, 05 Jan 2018 22:30:56 +0000
Message-ID: 
 <CAOPfGFjKGSjo5MSURH0UGtLHzzZ_7_rwaS=JGETHFMrKxGpE8g@mail.gmail.com>
Subject: How are debuginfo packages generated?
To: pgsql-pkg-yum <pgsql-pkg-yum@postgresql.org>
Content-Type: multipart/alternative; boundary="f403045e89c02fd11505620f0160"
List-Id: <pgsql-pkg-yum.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-pkg-yum@lists.postgresql.org>
List-Owner: <mailto:pgsql-pkg-yum-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-pkg-yum>
Precedence: bulk

--f403045e89c02fd11505620f0160
Content-Type: text/plain; charset="UTF-8"

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.

Yet, I know that PGDG's yum repositories have no problem getting debuginfo
packages. How do you get them?

Thanks,
Daniel

--f403045e89c02fd11505620f0160
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div><br></div><div>For quite some time, I&#39;ve be=
en building lightly modified PGDG packages, but I have never figured how PG=
DG&#39;s yum repo gets debuginfo packages. When I have built them, unless I=
 hack up the spec file to have &quot;%debug_package&quot; I do not get such=
 a debuginfo package. Clearly, that is not how the spec files work as-is in=
 pgrpms.</div><div><br></div><div>Yet, I know that PGDG&#39;s yum repositor=
ies have no problem getting debuginfo packages. How do you get them?</div><=
div><br></div><div>Thanks,</div><div>Daniel</div></div>

--f403045e89c02fd11505620f0160--