On Tue, Apr 26, 2022 at 02:49:26PM -0400, Nico Kadel-Garcia wrote:
>On Tue, Apr 26, 2022 at 2:10 PM Ewoud Kohl van Wijngaarden
><ewoud+fedora@kohlvanwijngaarden.nl> wrote:
>>
>> Hello everyone,
>>
>> There is an ancient version of Puppet in EPEL-7. Version 3.6 has been
>> EOL for ages now. https://binford2k.com/2016/11/22/puppet-3.x-eol/ has a
>> nice EOL overview:
>>
>> * Puppet 3 - 2016-12-31
>> * Puppet 4 - 2018-10-??
>> * Puppet 5 - 2021-02-??
>>
>> Puppet 6 requires a newer Ruby version than is available in EL7 so
>> rebasing the whole stack is not going to work. In theory you could use
>> SCLs but I think it's unrealistic to expect that.
>
>Rebuild it with the sco packages, namely rh-ruby25 ?

I'll state that I have extensive SCL knowledge, after working with it in
packaging Foreman. With that I'll clarify why I think it's unrealistic.

The primary reason is that I have no interest nor use for it at all.
Right my last EL7 machine is using the Puppet AIO package and I'll phase
it out soon.

Second, I don't know if anyone has done this and what the effects will
be. Providers such as the gem package provider will behave different.
You also won't have access to any Ruby gems that you may have installed.
As such it'll be a massive non-trivial migration for any user.

Speaking of gems, you will need to build all the dependent gems in the
SCL. This means a lot of gems need to be modified and released. From
experience I can tell you there are many things you can easily mess up,
as well as bugs in the SCL stack you need to work around (BZ1995018
being particularly nasty). Which brings me back to my primary reason: I
have no time for this.

BZ1995018: https://bugzilla.redhat.com/show_bug.cgi?id=1995018