Re: BUG #15768: Removed rpms and now require /etc/redhat-release

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Matt Harter <Matt(dot)Harter(at)genesys(dot)com>
Cc: Devrim Gündüz <devrim(at)gunduz(dot)org>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15768: Removed rpms and now require /etc/redhat-release
Date: 2019-06-21 15:03:58
Message-ID: 20190621150358.GA13774@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2019-Apr-18, Matt Harter wrote:

> Well whether or not it is officially supported, it still works on amazon linux, and since their default repositories are behind on postgres (which of course is really an amazon limitation) we have to manually add the repository. Since the recent change that added a required dependency (which is clearly NOT required for amazon linux), our previously working deploy pipelines are now blocked/broken. We have temporarily mitigated the issue by using rpm and explicitly ignoring the repositories dependencies, but that seems like a band-aid fix for the real problem which is that dependency shouldn’t be there. Why does a repository need to enforce the os it is on? If a consumer wants to do something “wrong” or against the documented way to do things, their issues are their problem.

I agree, and adding such a dep sounds like a strange change to make.
What was the rationale for that?

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2019-06-21 15:49:15 Re: BUG #15724: Can't create foreign table as partition
Previous Message Rozboril, Robert 2019-06-21 14:59:35 RE: PostgreSQL v11.3 - Records are deleted from child table if partition key of parent table is changed