@Willem Basson: Thanks for calling this out! I know that there have been a bunch of pieces getting some Debian 13 attention, but I think the puppetlabs-java module needs this PR to be reviewed by engineering and accepted: Add support for Debian 13 (trixie) by mika · Pull Request #613 · puppetlabs/puppetlabs-java I've already raised this PR with the team that was working on the Debian 13 support in January, but it's worth another ping and mentioning the Jenkins/Debian issue here. I've tagged the product managers in charge of this.

coming up to almost 2 months since this was mentioned in this channel, from what I can see using the base module is now broke and the PR (and follow on PR when you follow the chain through) has still yet to be merged and then released.

Yup, it hasn't been merged and released yet, but engineering did pick it up last week and created a new PR so they could run the tests against it (which did pass). Looks like it's requiring a review from somebody else on the modules team now before it can be merged: (PA-8354): Add support for Debian 13 (trixie) by span786 · Pull Request #622 · puppetlabs/puppetlabs-java

@Jason St-Cyr - Can this be picked up as we're 3 weeks on now? Also I've created a new MR to support Debian 13 and Ubuntu 26.04 as I've had to fork the module for 26.04 support as well. https://github.com/puppetlabs/puppetlabs-java/pull/623

it's comical, posting on linked in about round tables and updates to puppet modules yet core functional modules are unmaintained, perforce has time to make these round table brags about modules yet can't even manage it's own foundational process from the community. Just turn them over to thecommunity

Unfortunately, I can't take the time I spend on those module roundups and give that to the engineering team for more module releases. but It's the way that I can help, within my role. That said, one of the things I always ask in those articles is what things were missed specifically for this reason. There are quite a lot of community contributions that have not been processed, responded to, or merged and released. That's something the team is actively working on to build in a repeatable way to keep on top of modules better when there are competing priorities. @matt: You mentioned the 'base modules are dead', could you share which modules you feel have been not getting enough attention, or if it's a specific type of change you are looking for in those modules? @Trevor Rea: I'm going to ping the PM on the puppetlabs modules about this again. He's been working with the engineering team on working through some of the PRs on a bunch of different modules and I'm not sure if this one made it into the first round.

is there somewhere I can track outstanding debian 13 related issues? I need to choose between debian 12 and 13 for around 60 puppet roles

I don't think there's a central place tracking issues specific to Debian 13. Debian 13 is listed as a supported OS, so if issues were to come up you should be able to log support tickets to get them resolved.

core modules, postgres, mysql, apache, puppetdb, stdlib, haxproxy, kubernetes,

@matt: Thanks for the list of the ones that are key for you, I'll send these over to product management to make sure it goes in as input along with the tiering they are doing for which modules get attention more often.

Jason, it's still a bit of a scam, even modules that got an update say 6 months ago, didn't actually get any meaningful commits into them (I maybe over harsh on this) but it felt like typo changes while meaningful commits, such as major component/operating system versions that had tested PR's pending got ignored, it felt like a lip service bump, if you look at the change logs. These are core modules that a being recommended/approved/pushed by Puppet/Perforce, yet they lack version compatibility with operating systems that have been out 3+ years or support components that have been EOL for 2+ years and are no longer available, truthfully, it's not good enough from perforce, if the modules cannot be maintained by at the most basic level (reviewing other peoples PR's so the majority of the work has been done for them) against maintaining them as true component owners (providing active development and feature contribution) they should remove the puppet recommended tags. should put out statement saying 'these modules are now unsupported' or something, I have a bug request on one of these core modules just asking for clarification on the status of it - 6 months it's been open and I can't even get a response on if the modules are maintained any more https://github.com/puppetlabs/puppetlabs-postgresql/issues/1648 it's not good enough, perforce have failed and continue to fail and it's not being addressed no matter how much good intention or positive messaging there is, this is basic 101 requirements of a product that is 'owned' by perforce, you bought, it you develop it, and if you've not got the resources ask for help, I'm really really bored with perforces attitude, and I'm really bored of hearing about 'new great products' and 'commitment to the community' it's non-existent

I've been through the list of the modules I use as I've been doing an Ubuntu upgrade and while most of them do work on Ubuntu 26.04 they don't seem to be getting much attention basely purely on the last release date (not that that's a totally accurate indicator). puppetlabs-accounts - Jul 28th 2025 puppetlabs-apache - Nov 18th 2025 puppetlabs-apt - Dec 17th 2025 puppetlabs-firewall - Feb 9th 2026 puppetlabs-inifile - Feb 17th 2026 puppetlabs-java - Jul 18th 2025 - Not compatible with on Ubuntu 26.04 puppetlabs-mysql - Jul 30th 2025 - Module seems broken on Ubuntu 26.04 puppetlabs-ntp - Aug 11th 2025 - Module seems broken on Ubuntu 26.04 - I've switched to Chrony anyway puppetlabs-vcsrepo - Feb 26th 2025 I appreciate you can't magic up more time yourself if the people aren't there but I agree with Matt that there are lots of GitHub MRs and issues with no responses across the board.

Thank you both for this, and I agree that Perforce needs to do better with key modules that are used by many customers. I can use these lists of modules here to work with the rest of product and engineering to help align with the other priorities on the teams. I want my roundups to be full of community contributions on modules, and that won't happen if we don't get more community contributions reviewed and released!

@Trevor Rea I'd maybe check that list in compatible with ubuntu 26.04 some of the ones you list as compatible with 24.06 aren't even compatible with 24.04 - look at apache, support ends on 22.04 core module like apache and it doesn't support anything after 2022

There is one thing worse than negative feedback: no feedback. Negative feedback means folks still care and I love that.

I'm defining compatible in the loosest possible sense.