pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #16566: Consistently link latest repo RPM release to pgdg-redhat-repo-latest (ref #16074)
3+ messages / 3 participants
[nested] [flat]
* BUG #16566: Consistently link latest repo RPM release to pgdg-redhat-repo-latest (ref #16074)
@ 2020-07-31 19:09 PG Bug reporting form <noreply@postgresql.org>
0 siblings, 1 reply; 3+ messages in thread
From: PG Bug reporting form @ 2020-07-31 19:09 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: msaladna@apisnetworks.com
The following bug has been logged on the website:
Bug reference: 16566
Logged by: Matt Saladna
Email address: msaladna@apisnetworks.com
PostgreSQL version: 12.3
Operating system: CentOS 8/RHEL 8
Description:
Hello,
CentOS 8/RHEL 8 repo RPM is still inconsistently linked for v12. This was
reported back in October, bug #16074 for v11/RHEL 8. The issue now is with
v12 and RHEL 8 and related to a recent update as I haven't seen this for
some time.
rhel8/v11 (correct):
- pgdg-redhat-repo-latest.noarch.rpm
- pgdg-redhat-repo-42.0-11.noarch.rpm
rhel7/v12 (correct):
- pgdg-redhat-repo-latest.noarch.rpm
- pgdg-redhat-repo-42.0-11.noarch.rpm
rhel8/v12 (incorrect):
- MISSING
- pgdg-redhat-repo-42.0-11.noarch.rpm
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: BUG #16566: Consistently link latest repo RPM release to pgdg-redhat-repo-latest (ref #16074)
@ 2020-07-31 20:00 Devrim Gündüz <devrim@gunduz.org>
parent: PG Bug reporting form <noreply@postgresql.org>
0 siblings, 1 reply; 3+ messages in thread
From: Devrim Gündüz @ 2020-07-31 20:00 UTC (permalink / raw)
To: msaladna@apisnetworks.com,pgsql-bugs@lists.postgresql.org,PG Bug reporting form <noreply@postgresql.org>
Hi,
There is only one rpm for a distro. That -11 repo rpm internal release number.
Maybe I should have bumped it to -42 as well.
So, this is not an issue.
Regards, Devrim
On 31 July 2020 22:09:48 GMT+03:00, PG Bug reporting form <noreply@postgresql.org> wrote:
>The following bug has been logged on the website:
>
>Bug reference: 16566
>Logged by: Matt Saladna
>Email address: msaladna@apisnetworks.com
>PostgreSQL version: 12.3
>Operating system: CentOS 8/RHEL 8
>Description:
>
>Hello,
>
>CentOS 8/RHEL 8 repo RPM is still inconsistently linked for v12. This
>was
>reported back in October, bug #16074 for v11/RHEL 8. The issue now is
>with
>v12 and RHEL 8 and related to a recent update as I haven't seen this
>for
>some time.
>
>rhel8/v11 (correct):
>- pgdg-redhat-repo-latest.noarch.rpm
>- pgdg-redhat-repo-42.0-11.noarch.rpm
>
>rhel7/v12 (correct):
>- pgdg-redhat-repo-latest.noarch.rpm
>- pgdg-redhat-repo-42.0-11.noarch.rpm
>
>rhel8/v12 (incorrect):
>- MISSING
>- pgdg-redhat-repo-42.0-11.noarch.rpm
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: BUG #16566: Consistently link latest repo RPM release to pgdg-redhat-repo-latest (ref #16074)
@ 2020-07-31 20:33 Matt Saladna <matt@apisnetworks.com>
parent: Devrim Gündüz <devrim@gunduz.org>
0 siblings, 0 replies; 3+ messages in thread
From: Matt Saladna @ 2020-07-31 20:33 UTC (permalink / raw)
To: Devrim Gündüz <devrim@gunduz.org>; +Cc: pgsql-bugs@lists.postgresql.org
All other combinations of PostgreSQL + RHEL have a "latest" RPM that is
linked to -11. It is an inconsistency with how the repo is laid out for
PostgreSQL v12 and RHEL 8.
I brought this issue up in November as well (#16074), which was
acknowledged and fixed.
All of the following repos *contain both*
pgdg-redhat-repo-42.0-11.noarch.rpm and pgdg-redhat-repo-latest.noarch.rpm:
https://download.postgresql.org/pub/repos/yum/10/redhat/rhel-8-x86_64/
https://download.postgresql.org/pub/repos/yum/11/redhat/rhel-8-x86_64/
https://download.postgresql.org/pub/repos/yum/10/redhat/rhel-7-x86_64/
https://download.postgresql.org/pub/repos/yum/11/redhat/rhel-7-x86_64/
https://download.postgresql.org/pub/repos/yum/12/redhat/rhel-7-x86_64/
The following repo *does not* contain pgdg-redhat-repo-latest.noarch.rpm:
https://download.postgresql.org/pub/repos/yum/12/redhat/rhel-8-x86_64/
If pgdg-redhat-repo-latest.noarch.rpm is no longer supported, then I can
update my code that looks for "pgdg-redhat-repo-latest.noarch.rpm".
Based on the other locations having
"pgdg-redhat-repo-latest.noarch.rpm", it seems like a bug to me.
- Matt
On 7/31/2020 3:00 PM, Devrim Gündüz wrote:
> Hi,
>
> There is only one rpm for a distro. That -11 repo rpm internal release
> number.
>
> Maybe I should have bumped it to -42 as well.
>
> So, this is not an issue.
>
> Regards, Devrim
>
> On 31 July 2020 22:09:48 GMT+03:00, PG Bug reporting form
> <noreply@postgresql.org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 16566
> Logged by: Matt Saladna
> Email address: msaladna@apisnetworks.com
> PostgreSQL version: 12.3
> Operating system: CentOS 8/RHEL 8
> Description:
>
> Hello,
>
> CentOS 8/RHEL 8 repo RPM is still inconsistently linked for v12. This was
> reported back in October, bug #16074 for v11/RHEL 8. The issue now is with
> v12 and RHEL 8 and related to a recent update as I haven't seen this for
> some time.
>
> rhel8/v11 (correct):
> - pgdg-redhat-repo-latest.noarch.rpm
> - pgdg-redhat-repo-42.0-11.noarch.rpm
>
> rhel7/v12 (correct):
> - pgdg-redhat-repo-latest.noarch.rpm
> - pgdg-redhat-repo-42.0-11.noarch.rpm
>
> rhel8/v12 (incorrect):
> - MISSING
> - pgdg-redhat-repo-42.0-11.noarch.rpm
>
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2020-07-31 20:33 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-07-31 19:09 BUG #16566: Consistently link latest repo RPM release to pgdg-redhat-repo-latest (ref #16074) PG Bug reporting form <noreply@postgresql.org>
2020-07-31 20:00 ` Devrim Gündüz <devrim@gunduz.org>
2020-07-31 20:33 ` Matt Saladna <matt@apisnetworks.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox