| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | uj410228(at)gmail(dot)com |
| Subject: | BUG #19479: 04 is happening because your metadata is advertising a package version that is not actually present |
| Date: | 2026-05-15 06:41:22 |
| Message-ID: | 19479-b572b89cbcb8d325@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 19479
Logged by: Pratik Kumar
Email address: uj410228(at)gmail(dot)com
PostgreSQL version: 14.23
Operating system: Linux
Description:
I checked the live PGDG repository, and rhel-9-x86_64 currently has
postgresql14-libs-14.21-1PGDG.rhel9.7.x86_64.rpm and 14.22, plus
postgresql14-server-14.21 and 14.22 — I do not see 14.23 in that directory
yet.
That matters because PostgreSQL 14.23 was released on May 14, 2026, but the
Red Hat download page also says the project publishes RPMs through the Yum
repository and provides direct downloads from the same repo.
So the 404 is happening because your metadata is advertising a package
version that is not actually present on the server. The repo itself can only
be updated by the PostgreSQL PGDG maintainers; you cannot upload RPMs into
download.postgresql.org yourself. The official support path is to report it
through PostgreSQL’s bug/support process.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2026-05-15 11:11:37 | BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct |
| Previous Message | PG Bug reporting form | 2026-05-15 01:29:54 | BUG #19478: `dblink_close` can be used for injection. |