[Pkg-puppet-devel] Bug#950182: Bug#950182: Bug#950182: Puppet 5.5 EOL in November 2020

[Antoine Beaupré]

Control: severity -1 serious

Justification: this package depends on ruby 2.7, gone from bookworm. See
below.

On 2022-04-14 10:12:25, Gabriel Filion wrote:
> in current debian testing, ruby has been transitioned to 3.0 and judging 
> from the release history, puppet has not added support for ruby 3.0 
> until 7.8.0:
>
> https://puppet.com/docs/puppet/7/release_notes_puppet.html#enhancements_puppet_x-7-8-0-pup-11076
>
> and also, as was noted in #1009643 the puppet tests fail on 3.0 which 
> seems to indicate that supporting puppet 5.5 in debian testing will be 
> quite difficult.
>
> Because of that information I think we should aim for removing puppet 5 
> from testing and then move on to the discussion of packaging future 
> versions.
>
> that same argument about ruby 3.0 support would lead me to believe that 
> aiming for puppet 6 would be a mistake (that and the EOL date for puppet 
> 6 which will be very close to a debian release).

Agreed. Let's remove it for now. When we land a Puppet agent 7 here,
this bug can be closed and the package will migrate down to bookworm
again.

> in the #puppet channel on chat.libera.net, a couple poeple told me that 
> since puppet 4.x the differences in terms of manifests are mostly 
> additive and don't see many breakage at all between major versions, and 
> that would be true until at least puppet 7. so it should be possible for 
> users to jump from 5 to 7 directly

I proposed as much in the "policy" thread, so I think that would really
make a lot of sense. Worst case, this fails and we *also* need to
package Puppet server 6 in fasttrack.

Thanks for the heads up.

a.

-- 
Le péché est né avant la vertu, comme le moteur avant le frein.
                         - Jean-Paul Sartre