BUG #16074: Consistently link latest repo RPM release to pgdg-redhat-repo-latest

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: msaladna(at)apisnetworks(dot)com
Subject: BUG #16074: Consistently link latest repo RPM release to pgdg-redhat-repo-latest
Date: 2019-10-23 22:42:54
Message-ID: 16074-708f8cd50b2b93aa@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 16074
Logged by: Matt Saladna
Email address: msaladna(at)apisnetworks(dot)com
PostgreSQL version: 11.0
Operating system: RHEL 8
Description:

RHEL7 and prior repositories link the latest pgdg repo release to
pgdg-redhat-repo-latest.noarch.rpm. This is not the case with RHEL8:

RHEL7 with Postgres 11:
pgdg-redhat-repo-42.0-5.noarch.rpm 2019-Sep-27
13:28:13 5.8K application/x-redhat-package-manager
pgdg-redhat-repo-latest.noarch.rpm 2019-Sep-27
13:28:13 5.8K application/x-redhat-package-manager

And from RHEL8 with Postgres 11:
pgdg-redhat-repo-42.0-5.noarch.rpm 2019-Sep-27
13:25:39 9.9K application/x-redhat-package-manager

-latest is properly linked in RHEL8/Postgres 12, but not with 11, 10, or
9.6.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2019-10-24 07:25:50 BUG #16075: The favicon of https://www.postgresql.org is vague on MacBook Pro with retina display
Previous Message Bruce Momjian 2019-10-23 22:08:21 Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12