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 1uiwgf-000YxB-9i for pgsql-general@arkaria.postgresql.org; Mon, 04 Aug 2025 15:01:17 +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 1uiwgd-0021K6-N2 for pgsql-general@arkaria.postgresql.org; Mon, 04 Aug 2025 15:01:15 +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 1uiwgd-0021Jy-9A for pgsql-general@lists.postgresql.org; Mon, 04 Aug 2025 15:01:15 +0000 Received: from mail-pj1-x102d.google.com ([2607:f8b0:4864:20::102d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uiwga-000hej-1k for pgsql-general@lists.postgresql.org; Mon, 04 Aug 2025 15:01:14 +0000 Received: by mail-pj1-x102d.google.com with SMTP id 98e67ed59e1d1-312a806f002so766822a91.3 for ; Mon, 04 Aug 2025 08:01:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1754319672; x=1754924472; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=RncYWjhwnOT7OsaTePYepqDRSQdI7KPpqlYZzltU4aE=; b=hr+JFZGJLA/XZcTUsyyZP+ugcDOVeh2+zzCKg4VRNzwToYjBc+WAyfykZIclyn6EOK VZHfAPePg+KThYWNyt25IHR8c6MoZ3H0xDI//njeZtI/2TD/siXYJREPVGSouh9xXgyr VPIvpl5SZ3IvedhOhYeXhFnPEfAJsYNuL7DRbu1j2oqzVPvKJz5q174xQWfRVn1sKcOX Tw30tUtHc8pOHGsXCGMMwiyqtc0H41PRR7UPbPPkiPJmome23wVyNru7OmNxQL+oRR2h +qLaaAaphSLgMfr2JTM2W12kEeV05TIt2Iy4DHTBTGSFYf4bfkndW3mJxieNANe3Flww siqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1754319672; x=1754924472; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=RncYWjhwnOT7OsaTePYepqDRSQdI7KPpqlYZzltU4aE=; b=nd8dqNmee5Gpnij4uGaIR1MNpkayvh4LehZWOD5IPhU3iA7dPfKp2tGz3TDtQe6+0M HFD04UE7cUe8hUzMDB/ToXbmwDy1lTR1FqgzCjzaThOUptOqxb54YOxPcVS3FEbs23xr 4+EoihmUgj8YiID3z1R1WzaOb4p7AA8lUd8GCj0pBF94qqMiTIz+7qzThemmP+eBMVaE SZmy1zm1DK5wSqrpWb5Pr+fxEBBx24imaPX22bem8zbAf0XKFhuRaA4mnJPTQZgguId/ dbNHZjUCN9Qthv8T8CG7IBqrddl5B9E7dAqdo8Y3pCn4ndudAZPtIk2cPU6fZEgxX6pu 5+kw== X-Gm-Message-State: AOJu0YwSn+AM8m7u3V7rF2G9xcvqvLGZpob/Xcgu5yx9QhdA7PYQer14 IaRXkhr7RdOtScTyfdSl5918tLveVeGSCwjV6OXL6OWSjuOc8oXCZrZYG8Ze3pEAfDls2/HnTrU SCQccKcEWRGejXLhbp858quF5onehwq4Hfr9v X-Gm-Gg: ASbGncvEijeL1iGPwP8YgxnUkOBrzmvAbLMrUQRz5GFl0/14JP7hMkEKh+pSOshnNcM 85E0v6b9wKzx1GUeKkweGxjEMBV84y3zwSVBeN13a5ydVsS+deHDIdAvSRHG/HZHU1R9szCQdxV 7lNjmtERwx4S5SlXiZdNuP5m2uLFiGp/G9mExOVHaAFfn05NGsCilWOKDXL00vUuEyrtRAyfF4x ppk1CYT X-Google-Smtp-Source: AGHT+IHvspQaXbqPhJVgG9DufsflJ6C47+yef5Aqd4jcWHL1DglxTZ5QadwN5m28tRDdVl1Bwrx3i2Eu27nsmqbd8gA= X-Received: by 2002:a17:90b:3887:b0:31e:ff94:3fae with SMTP id 98e67ed59e1d1-321162a2892mr5616516a91.4.1754319671420; Mon, 04 Aug 2025 08:01:11 -0700 (PDT) MIME-Version: 1.0 From: =?UTF-8?B?QWxlxaEgWmVsZW7DvQ==?= Date: Mon, 4 Aug 2025 17:01:00 +0200 X-Gm-Features: Ac12FXzXaJRWCM3hwRSlgiSI3lZZy_HmLv7gZ4wd8qC_rZZWnmcHZRw2Mmw0pUs Message-ID: Subject: PGDG16 repository error - repomd.xml.asc is empty To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000d66df2063b8b608c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d66df2063b8b608c Content-Type: text/plain; charset="UTF-8" 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=* --enablerepo=pgdg17 info postgresql17 Last metadata expiration check: 0:00:10 ago on Mon 04 Aug 2025 02:25:55 PM 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 PostgreSQL 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=* --enablerepo=pgdg16 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/repodata/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=31536000 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 = 0 in /etc/yum.repos.d/pgdg-redhat-all.repo for pgdg16. Thanks for fixing or providing advice on how to securely handle this issue. Kind regards Ales Zeleny --000000000000d66df2063b8b608c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,
I've found that PGDG16 repositor= y 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
De= scription =C2=A0: PostgreSQL is an advanced Object-Relational database mana= gement 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 ne= ed to
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: access a Postgre= SQL 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 serv= er, 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 Post= greSQL 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 Post= greSQL
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: server, you nee= d this package. You also need to install this package
=C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: if you're installing the postgresql17-= server package.

$ yum -y --disablerepo=3D* --enablerepo=3Dpgdg16 inf= o postgresql16
PostgreSQL 16 for RHEL / Rocky / AlmaLinux 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': repomd.xml GPG sign= ature verification error: gpgme_op_verify() error: No data


The PGP signature for PGDG16 repo is empty:

=
$ curl -I https://download.postgr= esql.org/pub/repos/yum/16/redhat/rhel-9-x86_64/repodata/repomd.xml.asc<= /div>HTTP/2 200
server: nginx
content-type: application/octet-stream=
last-modified: Sun, 03 Aug 2025 15:33:48 GMT
etag: "688f815c-0&= quot;
strict-transport-security: max-age=3D31536000
accept-ranges: by= tes
date: Mon, 04 Aug 2025 14:17:10 GMT
via: 1.1 varnish
age: 1437= 8
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=C2=A0r= epo_gpgcheck =3D 0 in=C2=A0/etc/yum.repos.d/pgdg-redhat-all.repo for pgdg16= .

Thanks for fixing or providing advice on how to = securely handle this issue.

Kind regards Ales Zele= ny
--000000000000d66df2063b8b608c--