Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uiwzZ-000eUB-7O for pgsql-general@arkaria.postgresql.org; Mon, 04 Aug 2025 15:20:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uiwzX-002ApS-4i for pgsql-general@arkaria.postgresql.org; Mon, 04 Aug 2025 15:20:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uiwzW-002Ane-MD for pgsql-general@lists.postgresql.org; Mon, 04 Aug 2025 15:20:46 +0000 Received: from mail-pj1-x1033.google.com ([2607:f8b0:4864:20::1033]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uiwzT-000hne-2I for pgsql-general@lists.postgresql.org; Mon, 04 Aug 2025 15:20:45 +0000 Received: by mail-pj1-x1033.google.com with SMTP id 98e67ed59e1d1-312a806f002so770349a91.3 for ; Mon, 04 Aug 2025 08:20:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1754320844; x=1754925644; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=x90KbmqUOlkz09dGKh+Xij1IlVb6pqe/MFlW4Eh1H7U=; b=Rq3RQO3lnOWiY7l7hcdKLqlPce3lilMc57opZn1KfOpHXMlxDy+gyQJ0FpcJ8Txk0A zcDaPxSJmfV3HMo4ZSlqJdx3h7Rg2gi2vdkyChgfKKjAk6qsizT1C0Ke5TKf0fGd94VM QeBdTi7FFmCa3QGM9vGvSfun6q4FGGUnGfm8Ac38tkx+StcXox61/Wm2/rz93vKNWOZf vfnv1Wd1ps6Xt5msrxts5cee4mYNacOsxFxgQ9FmjcwtkPHNFiFCUeDyb/UAK/jRDSNm LoxfXgm2eX1cIZHlj+oVwbRETCJa69zQzEc6gRZDIBtLyC9THiIWd9+NT1nqGolmUk1V bWWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1754320844; x=1754925644; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=x90KbmqUOlkz09dGKh+Xij1IlVb6pqe/MFlW4Eh1H7U=; b=YWhPsflku8k95e5MhzeoYg9S9Q3m0OKS+oCHj3pY6OHyAAHCMKFGDABxnVtYEmFCqA F9RSvUkA3l4sbjIHi1jX76uIdmvKOKjRP5bG0g7J8k69ih9R8uP+TrNjkVv5HFJx4IG9 Ssgl0GJnpf7opl8jLDtoWOAC8FANrh2BH88yDN3SYkzaMuQRcngnvqohGuzrCmCA4RMD w50+3T7k74XIgGq71idB602mor5uKLuV4Cnk2W6AnhX9wWRIAC5fjWY4aut6nFG0w9v4 vEF2wptRPxmiV3KKBpnM1Ei7uR7YaObaVvDUWpBMkZIEhlKp2pHvwIffbRHxFfOcMQAg 7siQ== X-Gm-Message-State: AOJu0YyH5nloLzxNOC2FZelN50h9dlGmfMcgm84KF6jOH1f9/lhWSEcp RwgMcuRqgAL0/g9SJs+j+WvUiPRrTrW8Op73+gsmAC02FVw9BpSoo747oO9uZXhVQWhQUUOMWjC fk/hL0AN6OIKxyMJUFQ1k1JPbVdTQrWV+7Lbw X-Gm-Gg: ASbGncsWLURN5oYuNyk/8WioOLO6GkIi0FnbYI7ZMT0Hsb9bEH7muewgx9fQj5lJ+S7 O35Rs99vPGssuvRDBRCgcQo75IKSEpWNAQSzbh5uDxRLJ0kqorFeo9oimTNg01YOKN4Ftl5x0/O 34817eO7jQK7l3PLtOmsSIuWJglJPUZrXgGvHo5UbmJyEwe4eKrKe0461JPwbZs3CXTH6cu2tI/ 7aPGutw X-Google-Smtp-Source: AGHT+IFKJ0EVuoaaiYScPp04uC24bJAQXOMKOpcKRb8VfOMCvoBECTOxzztOr5JO3BHZ4Ynzlz0yJWlTJvqIqfFB5DY= X-Received: by 2002:a17:90b:1c10:b0:312:e9d:4001 with SMTP id 98e67ed59e1d1-321162d2568mr5307316a91.8.1754320843738; Mon, 04 Aug 2025 08:20:43 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?B?QWxlxaEgWmVsZW7DvQ==?= Date: Mon, 4 Aug 2025 17:20:32 +0200 X-Gm-Features: Ac12FXwk0A1W3qpTUZED1XQwQlvS0PEz5ZT-XIdpFhsYezENbJNteq8JK-nJYmw Message-ID: Subject: Re: PGDG16 repository error - repomd.xml.asc is empty To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000b694e9063b8ba694" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b694e9063b8ba694 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Probably duplicate for BUG #19009 / BUG #19010. po 4. 8. 2025 v 17:01 odes=C3=ADlatel Ale=C5=A1 Zelen=C3=BD napsal: > Hello, > I've found that PGDG16 repository access is failing (while last Thursday > it worked): > > Example - pgdg 17 works, pgdg16 doesn't work: > > $ yum repolist pgdg16 pgdg17 > repo id repo name > status > pgdg16 PostgreSQL 16 for RHEL / Rocky / AlmaLinux 9 - x86_64 > enabled > pgdg17 PostgreSQL 17 for RHEL / Rocky / AlmaLinux 9 - x86_64 > enabled > > $ yum -y --disablerepo=3D* --enablerepo=3Dpgdg17 info postgresql17 > Last metadata expiration check: 0:00:10 ago on Mon 04 Aug 2025 02:25:55 P= M > UTC. > Available Packages > Name : postgresql17 > Version : 17.5 > Release : 3PGDG.rhel9 > Architecture : x86_64 > Size : 1.9 M > Source : postgresql17-17.5-3PGDG.rhel9.src.rpm > Repository : pgdg17 > Summary : PostgreSQL client programs and libraries > URL : https://www.postgresql.org/ > License : PostgreSQL > Description : PostgreSQL is an advanced Object-Relational database > management system (DBMS). > : The base postgresql package contains the client programs > that you'll need to > : access a PostgreSQL DBMS server. These client programs can > be located on the > : same machine as the PostgreSQL server, or on a remote > machine that accesses a > : PostgreSQL server over a network connection. The PostgreSQ= L > server can be found > : in the postgresql17-server sub-package. > : > : If you want to manipulate a PostgreSQL database on a local > or remote PostgreSQL > : server, you need this package. You also need to install > this package > : if you're installing the postgresql17-server package. > > $ yum -y --disablerepo=3D* --enablerepo=3Dpgdg16 info postgresql16 > PostgreSQL 16 for RHEL / Rocky / AlmaLinux 9 - x86_64 > > > 0.0 B/s | = 0 > B 00:00 > Error: Failed to download metadata for repo 'pgdg16': repomd.xml GPG > signature verification error: gpgme_op_verify() error: No data > > > The PGP signature for PGDG16 repo is empty: > > $ curl -I > https://download.postgresql.org/pub/repos/yum/16/redhat/rhel-9-x86_64/rep= odata/repomd.xml.asc > HTTP/2 200 > server: nginx > content-type: application/octet-stream > last-modified: Sun, 03 Aug 2025 15:33:48 GMT > etag: "688f815c-0" > strict-transport-security: max-age=3D31536000 > accept-ranges: bytes > date: Mon, 04 Aug 2025 14:17:10 GMT > via: 1.1 varnish > age: 14378 > x-served-by: cache-fra-etou8220082-FRA > x-cache: HIT > x-cache-hits: 64 > x-timer: S1754317030.249893,VS0,VE0 > content-length: 0 > > The only workaround I've found is to set repo_gpgcheck =3D 0 > in /etc/yum.repos.d/pgdg-redhat-all.repo for pgdg16. > > Thanks for fixing or providing advice on how to securely handle this issu= e. > > Kind regards Ales Zeleny > --000000000000b694e9063b8ba694 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Probably duplicate for BUG #19009 /=C2=A0BUG #19010.
=
po 4. 8. 2025 v=C2=A017:01 odes=C3=ADlatel Ale=C5=A1 Zelen= =C3=BD <zeleny.ales@gmail.com> napsal:
<= div dir=3D"ltr">
Hello,
I've found that PGDG16 repository= access is failing (while last Thursday it worked):

Example - pgdg 17 works, pgdg16 doesn't work:

$ yum repolist pgdg16 pgdg17
repo id=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= repo name=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 =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 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 status
pgdg16=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0PostgreSQL 16 for RHEL / Rocky / AlmaLinux 9 - x86_64=C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 enabled
pgdg17=C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0PostgreSQL 17 for RHEL / Rocky / AlmaLinux 9 - x86_64= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 enabled

$ yum -y --disablerepo=3D* --enablerepo=3Dpgdg= 17 info postgresql17
Last metadata expiration check: 0:00:10 ago on Mon= 04 Aug 2025 02:25:55 PM UTC.
Available Packages
Name =C2=A0 =C2=A0 = =C2=A0 =C2=A0 : postgresql17
Version =C2=A0 =C2=A0 =C2=A0: 17.5
Relea= se =C2=A0 =C2=A0 =C2=A0: 3PGDG.rhel9
Architecture : x86_64
Size =C2= =A0 =C2=A0 =C2=A0 =C2=A0 : 1.9 M
Source =C2=A0 =C2=A0 =C2=A0 : postgresq= l17-17.5-3PGDG.rhel9.src.rpm
Repository =C2=A0 : pgdg17
Summary =C2= =A0 =C2=A0 =C2=A0: PostgreSQL client programs and libraries
URL =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0: https://www.postgresql.org/
License =C2=A0 =C2=A0 =C2=A0= : PostgreSQL
Description =C2=A0: PostgreSQL is an advanced Object-Relati= onal database management system (DBMS).
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0: The base postgresql package contains the client programs= that you'll need to
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0: access a PostgreSQL DBMS server. These client programs can be located = on the
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: same machine as= the PostgreSQL server, or on a remote machine that accesses a
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: PostgreSQL server over a network= connection. The PostgreSQL server can be found
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0: in the postgresql17-server sub-package.
=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: If you want to manipulate a PostgreSQL database on a= local or remote PostgreSQL
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0: server, you need this package. You also need to install this packag= e
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: if you're instal= ling the postgresql17-server package.

$ yum -y --disablerepo=3D* --e= nablerepo=3Dpgdg16 info postgresql16
PostgreSQL 16 for RHEL / Rocky / Al= maLinux 9 - x86_64 =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 =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 =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 =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 =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 =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 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 0.0 =C2=A0B/s | =C2=A0 0 =C2=A0B =C2=A0 =C2=A0 00:00 = =C2=A0 =C2=A0
Error: Failed to download metadata for repo 'pgdg16= 9;: repomd.xml GPG signature verification error: gpgme_op_verify() error: N= o data


The PGP signature for PGDG16 repo i= s empty:

HTTP/2 200
server: nginx<= br>content-type: application/octet-stream
last-modified: Sun, 03 Aug 202= 5 15:33:48 GMT
etag: "688f815c-0"
strict-transport-security= : max-age=3D31536000
accept-ranges: bytes
date: Mon, 04 Aug 2025 14:1= 7:10 GMT
via: 1.1 varnish
age: 14378
x-served-by: cache-fra-etou82= 20082-FRA
x-cache: HIT
x-cache-hits: 64
x-timer: S1754317030.24989= 3,VS0,VE0
content-length: 0

The only w= orkaround I've found is to set=C2=A0repo_gpgcheck =3D 0 in=C2=A0/etc/yu= m.repos.d/pgdg-redhat-all.repo for pgdg16.

Thanks = for fixing or providing advice on how to securely handle this issue.
<= div>
Kind regards Ales Zeleny
--000000000000b694e9063b8ba694--