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 1ujCfp-004L24-Uh for pgsql-general@arkaria.postgresql.org; Tue, 05 Aug 2025 08:05:30 +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 1ujCfo-008P7W-RN for pgsql-general@arkaria.postgresql.org; Tue, 05 Aug 2025 08:05:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ujCfo-008P7N-F5 for pgsql-general@lists.postgresql.org; Tue, 05 Aug 2025 08:05:28 +0000 Received: from mail-pj1-x102e.google.com ([2607:f8b0:4864:20::102e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1ujCfl-000qGU-2K for pgsql-general@lists.postgresql.org; Tue, 05 Aug 2025 08:05:28 +0000 Received: by mail-pj1-x102e.google.com with SMTP id 98e67ed59e1d1-31ec977d203so1075004a91.0 for ; Tue, 05 Aug 2025 01:05:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1754381123; x=1754985923; 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=daisW6+pznARIlrV81fe84Dsl2UofnSpnpTMwE8cYOs=; b=bU3+JO1+hJVht/6Yjm5haEXjUJPcYm/kKYTOIEnY6pnFJ1P+0FXtYwkoEy0AAUW3t/ XjE1ZtbKh76/s6/lZzmlEdOxwd6GxxNyO0riYdwBjdqdLNWaacvxeuG7B2aIav29H17R qdYbW11/L/MV5GVsj1C9d4+CHeHzsxOmcmq8FiGgSrlxjNQFQV62CMb11KDeJ/Lv7edF 6vgCrEuq/v91jyhsBnmE2taiT1VG/4kHcJnsOpOTR9CWKA6Wl04p2I9ItaSsEfG0yTTw G9yiyRxGfeWs6Qk4PQohDDE1TEvcf19dHOTWB5qM7n3SLiO96cqIkoFo8eTLoWNGSqry llew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1754381123; x=1754985923; 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=daisW6+pznARIlrV81fe84Dsl2UofnSpnpTMwE8cYOs=; b=hXMH5OBpyRBV1bHZ7OQJrKgGH2LoXGhkgY7LRldoxFjO/Nu8kAbDl/k6U8Qh7f/8Si duKK8hxrzpwDE7WazKx+ZG/zlMwKp7O8RYQNCR9a+uy0oCdW+m4hjZbIlt/ErWn78Cuh rGavULY8JkBkA/L2BjL9B7wXZ0T7bY6ZClpM7v/+5I7z4CS00sdVsBGeJjrciyyJvPid crkQqwGL1ySnZFEF+fQ7haJ4rSPXurIIWlkP6A6f5hKjKKXw8//eIFcYGDSB0+5Qqc/9 VvqkWJQMBGdFCp4m3l6KJKqlpIxXOtRRdgGswRMH2C5gi2ogXQL38gcDgQf9k3OtxrhY CvYw== X-Gm-Message-State: AOJu0YwE1f/0G2lEKC4v9Xuw6HfJ+gKOLJvWB+wn4lb/2S0gtRacAhoU IXGGq0Nz/mtN2mGFR09ll8RJmtowLxzZEdhZQlVrg+bmMf48HHYlBW5inER/UsPPk3Qw2pXti8R ZX2mQJQ47sGnO5oTNt9bfx+rpzaAeUKNjQ1g1 X-Gm-Gg: ASbGncsfpku++V3VL8PWujBpHhT4N06a6hYOuB2h54E2sYwvml6tE8ewPPMpJgoov6V J9iTtfR6Jq+3h9xRqQBUnoFRpdZWbfw8PrlteQfCh8fnY9RjKoiq2qE681a7wnUlJbuQhjGRCVx v4hv9MW0lx1Wz8wh7X1WWwyF7iBzLMOJz16rlgK88alHoi2aPHvkGoTxVbsvNyaZNV8YBDZDByJ XDeihZJ X-Google-Smtp-Source: AGHT+IFvyykoBsqP/6G1Kch44u8C8n4QE2+uR1LtkG73zi+ujrtudwkhF0j9FYy2XvGsGqFRHPRH6M1aU1clDWIoAWc= X-Received: by 2002:a17:90b:1b06:b0:31f:24c2:16cb with SMTP id 98e67ed59e1d1-321162cd92dmr7091880a91.6.1754381122742; Tue, 05 Aug 2025 01:05:22 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?B?QWxlxaEgWmVsZW7DvQ==?= Date: Tue, 5 Aug 2025 10:05:11 +0200 X-Gm-Features: Ac12FXxXisml4oEmRSNC8EQIQm-wa_o8r73MsMG0zzpSqYDyF7RbWh4eeP_-B1s Message-ID: Subject: Re: PGDG16 repository error - repomd.xml.asc is empty To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000009f2f52063b99af9b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000009f2f52063b99af9b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable The pgdg16-debuginfo repository suffers from another issue (yesterday it worked): Failed to download metadata for repo 'pgdg16-debuginfo': repomd.xml GPG signature verification error: Bad GPG signature Kind regards Ales Zeleny po 4. 8. 2025 v 17:20 odes=C3=ADlatel Ale=C5=A1 Zelen=C3=BD napsal: > 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 >> 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 ca= n >> 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 loca= l >> 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/re= podata/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 >> issue. >> >> Kind regards Ales Zeleny >> > --0000000000009f2f52063b99af9b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The=C2=A0pgdg16-debuginfo repository suffers from ano= ther issue (yesterday it worked):

Failed to downlo= ad metadata for repo 'pgdg16-debuginfo': repomd.xml GPG signature v= erification error: Bad GPG signature

Kind regards = Ales Zeleny


po 4. 8. 2025 v=C2=A0= 17:20 odes=C3=ADlatel Ale=C5=A1 Zelen=C3=BD <zeleny.ales@gmail.com> napsal:
Probably duplicate for= BUG #19009 /=C2=A0BUG #19010.

po 4. 8. 2025 v=C2=A017:01 odes=C3=ADlatel Al= e=C5=A1 Zelen=C3=BD <zeleny.ales@gmail.com> napsal:
Hello,
I'= ve found that PGDG16 repository access is failing (while last Thursday it w= orked):

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
pgdg1= 6=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0PostgreSQL 16 for RHEL / Rocky / AlmaLin= ux 9 - x86_64=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 enable= d
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=3Dpgdg17 info postgresql17
Last metadata expiration c= heck: 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
Release =C2=A0 =C2=A0 =C2=A0: 3PGDG.rhel9
Architectu= re : x86_64
Size =C2=A0 =C2=A0 =C2=A0 =C2=A0 : 1.9 M
Source =C2=A0 = =C2=A0 =C2=A0 : postgresql17-17.5-3PGDG.rhel9.src.rpm
Repository =C2=A0 = : pgdg17
Summary =C2=A0 =C2=A0 =C2=A0: PostgreSQL client programs and li= braries
URL =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: https://www.postgresql.org/
Licens= e =C2=A0 =C2=A0 =C2=A0: PostgreSQL
Description =C2=A0: PostgreSQL is an = advanced Object-Relational database management system (DBMS).
=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: The base postgresql package contain= s 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 pro= grams 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 s= ub-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 Pos= tgreSQL 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 t= o 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 info 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 signature verification error: gpgme_= op_verify() error: No data


The PGP signatu= re for PGDG16 repo is empty:

HTTP/2 20= 0
server: nginx
content-type: application/octet-stream
last-modif= ied: Sun, 03 Aug 2025 15:33:48 GMT
etag: "688f815c-0"
stric= t-transport-security: max-age=3D31536000
accept-ranges: bytes
date: M= on, 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-time= r: S1754317030.249893,VS0,VE0
content-length: 0

<= /div>
The only workaround I've found is to set=C2=A0repo_gpgcheck = =3D 0 in=C2=A0/etc/yum.repos.d/pgdg-redhat-all.repo for pgdg16.
<= br>
Thanks for fixing or providing advice on how to securely hand= le this issue.

Kind regards Ales Zeleny
--0000000000009f2f52063b99af9b--