Well whether or not it is officially supported, it still works on amazon linux, and since their default repositories
arebehind on postgres (which of course is really an amazon limitation) we have to manually add the repository. Since
therecent change that added a required dependency (which is clearly NOT required for amazon linux), our previously
workingdeploy pipelines are now blocked/broken. We have temporarily mitigated the issue by using rpm and explicitly
ignoringthe repositories dependencies, but that seems like a band-aid fix for the real problem which is that dependency
shouldn’tbe there. Why does a repository need to enforce the os it is on? If a consumer wants to do something “wrong”
oragainst the documented way to do things, their issues are their problem.
On 4/18/19, 4:07 AM, "Devrim Gündüz" <devrim@gunduz.org> wrote:
Hi,
On Wed, 2019-04-17 at 12:20 +0000, PG Bug reporting form wrote:
> Amazon linux does not have /etc/redhat-release and our pipelines are broken
> because the repositories we were using to add to yum are no longer there
> without requiring /etc/redhat-release. We are a CI/CD system so manually
> adding this is not an option.
Amazon Linux support was removed years ago actually. I just made sure that our
repo file reflects that.
Regards,
--
Devrim Gündüz
Open Source Solution Architect, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR
