Hi there,
I'm just chiming in to add yet another object on the scale:
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).
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
On Thu, 31 Mar 2022 11:24:34 -0400 =?utf-8?Q?Antoine_Beaupr=C3=A9?=
<anar...@debian.org> wrote:
On 2022-03-31 17:05:19, Thomas Goirand wrote:
> On 3/29/22 21:08, Antoine Beaupré wrote:
>> On 2020-02-02 13:06:42, Thomas Goirand wrote:
>>
>> [...]
>>
>>> FYI, I packaged and uploaded the first 2 so far, but can't push to Git.
>>> Please set me as maintainer or owner, so I can do that.
>>>
>>> Note that I'm doing a git based workflow, packaging upstream tags,
>>> rather than using pristine-tar. If this bothers anyone, please let me
>>> know (but please only complain about the workflow if you really have the
>>> intention to contribute to the packaging, otherwise you're just getting
>>> on my way to be efficient for no reason).
>>
>> Not sure I'm picking the right message to reply to here, but here we go.
>>
>> I see that you uploaded 6.16.0-1 to experimental back in December 2020:
>>
>> https://tracker.debian.org/news/1205795/accepted-puppet-6160-1-source-into-experimental/
>>
>> Is that package in any shape to ship with bookworm? It would be great to
>> start this transition to get the package down into testing soon...
>
> Uploading it will break current puppet-master. Unless we have a solution
> to replace it, I don't want to do that...
I understand that, but my perspective is that we *want* to break the
current, 5.5 puppet master. We do *not* want to ship that in
bookworm. So breaking it is acceptable in that sense, to me.
But I guess it's pointless to keep arguing that same point. :)
--
The survival of humans and other species on planet Earth in my view can
only be guaranteed via a timely transition towards a stationary
state, a world economy without growth.
- Peter Custers
