Re: pgbouncer-1.7.2-7.rhel6.x86_64.rpm fails to install on AMI

On Wed, Oct 18, 2017 at 1:17 AM Magnus Hagander <magnus(at)hagander(dot)net> wrote:

> I guess our experiences are different. I've never had the need for kernel
> level bugs on such instances. I have had countless of customers had their
> stuff broken by random incompatible upgrades pushed out in a way that even
> Fedora wouldn't do. Those problems all went away when people stopped using
> Amazon Linux.
>

Yeeeah. I've hit a couple, and when they bite, it's kind of
catastrophically difficult to do anything about it. They're the only ones
in the position to do efficient debugging.

> (And of course, a good way to get around the ancientness of centos 6 is to
> use centos 7)
>

7 is often not as new as Amazon Linux (modulo systemd?), for better and for
worse.

> Anyway. A fast moving distro with large number of backwards incompatible
> changes is obviously a huge hassle for the people maintaining the RPMs. I
> can't really fault them for not dealing with that, since it's on volunteer
> basis. Might be selection bias that makes them not exposed to the userbase.
>

It's a fast moving target for sure. And who will appreciate it? And how
long should one support old versions of Amazon Linux given their frequency
(it probably ca't be long?) Hard to say. It doesn't make much sense to
support it akin to CentOS 6, that's for sure.

I think the first step is to survey the wreckage of trying to build the
entire suite of packages. I have no idea how to do that, though.