Missing Puppet packages for Debian 12 (Bookworm)

[smortex]

Hello!

Debian 12 AIO packages for Puppet-Agent are now available (see https://github.com/puppetlabs/puppet/issues/9149).

We now need PuppetServer (this issue) and PuppetDB (https://github.com/puppetlabs/puppetdb/issues/3950) packages for this operating system :grin:.

[tyybbi]

Any updates on this? It seems that Foreman has the bookworm packages ready, but this issue is blocking the release. Also, concerning the upcoming EL7 EOL, people would prefer to migrate their puppetserver instances to Debian 12 instead of 11, if possible.

[tuxmea]

Debian 11 is EOL quite soon. ~2024-07 When can we expect Puppet Server and PuppetDB packages for Debian 12? https://wiki.debian.org/DebianReleases

[alaunay]

In 15 days, it will be a year since Debian 12 has been released. Very classy move, puppet.

[Valantin]

Hi all, we need to move to debian 12 in our infrastructure to be compliant to our security policy.

Any news?

[ministicraft]

Same for us

[h0tw1r3]

https://github.com/puppetlabs/ezbake/pull/629

[justinstoller]

We've had a lot of churn in who manages OS additions. Thank you all for your interest and especially @h0tw1r3 for the PR. I do not see myself getting ezbake released in time for the next release (feature complete is today) but will try to get it in for the release after that (so in 8-10 weeks), along with Ubuntu 24.04 support.

Feel free to ping me directly if you don't see any movement on this in the next 6 weeks.

[alaunay]

It's been almost a year since Debian 12 has been released. Maybe you could make a small effort to support it quickly, and not in 3 months...

[binford2k]

Let's remember to be kind here. Don't forget that you're asking engineers to go above and beyond the business priorities they're assigned to work on.

[alaunay]

I fail to see where I'm not kind. I just remarked that we're waiting for that for a year, the first ticket mentioning this was created in February 23, and for quite a few of us, puppetserver is the last Debian 11 we have, and it will be EOL in a month.

So, asking to push for a small change, which should have been done eons ago, on a release yet to come, and not putting us at odds with the security guys, does not seem far fetched. Especially if this cannot happen between releases, and thus not having to wait until October.

Pushy, yes. With very good reasons. Unkind, no.

[binford2k]

And you're absolutely accurate in that. But this is an engineering forum read by engineers doing their best to meet community needs above and beyond what the business has prioritized and filled their backlog with. Poking fun at them with remarks like "classy move" is extremely not fair to the hard work they're doing.

A more productive form of feedback would be to toss a ⬆️ or a 👍 on https://github.com/puppetlabs/community/discussions/65 where product decision makers can see and quantify support for this platform.

[bastelfreak]

the business priorities they're assigned to work on.

And that's the issue here. What are those priorities? I mentioned that so often: There is probably a group of product owners or similar that make decisions. Why isn't that communicated? Why don't those people come to office hours to announce their agenda? There are probably many skilled engineers at Puppet/Perforce working on important things. But that's in the dark. And the issues that we see in the community and as partners won't get prioritized, often we do not even get an answer. And to make it worse Puppet does a lot of gatekeeping by keeping many of the pipelines and repos internal and documentation doesn't exist for many things. Puppet Inc navigated itself into a corner up to a point where the community cannot reliably provide patches to enable for example Debian 12 builds.

Edit because Ben responded while I was typing:

But this is an engineering forum

How can we as a community or partners reach managers? So far I wasn't really successful in the past months and I really tried hard.

So what are we supposed to do besides keeping asking just to hope that someone that can make decisions actually responds?

[alaunay]

Poking fun at them with remarks like "classy move" is extremely not fair to the hard work they're doing.

The correct quote is "Very classy move, puppet." . puppet. Not the engineers: the company. So yes, I'm quite unhappy with puppet inc. I've no idea who works there or not, and all the tickets, issues or mastodon toots have been at the best answered with "yes, someday".

As a business ourselves, managing puppetserver for multiple clients, which are asking weekly "why isn't our puppetserver still updated to deb12 according to our guidelines", to which we can only answer "meeeh", we're wondering if we shouldn't start exploring other solutions.

[binford2k]

Words have meaning and impact, which you've demonstrated well by being upset when it's insinuated that you spoke unkindly.

Articulating your needs is welcome and productive. It motivates engineers to continue going above and beyond to be helpful and it also helps quantify platform demand so that business priorities can adjust.

Couching this as nothing more than insults does the opposite.

Thank you for expanding on your needs in your fourth comment. Adding that context to the discussion thread as well will surface it to the relevant PMs.

[binford2k]

@bastelfreak I've poked the platform PMs to respond to the discussion thread.

[bastelfreak]

Thanks! ❤️

[bastelfreak]

Now who are the platforms PMs and will we get a response here?

[bastelfreak]

Hi, are there even platforms PMs anymore or do they simply ignore community requests?

[davidsandilands]

@GSPatton ? and I'm not sure Aniruddha has a github account