I mean, with the right queuing mechanism and tooling, webhook go itself could orchestrate runs or make using

choria

is a better option, but I haven't gone back to that yet. And this issue is largely applicable to those that really want to use bolt to run r10k AND are still running it on physical servers. The orchestrator support will likely be disabled during compile time on the Docker containers/kubernetes deployments, preferring instead to use volumes and PVs/PVCs to ensure puppet code is synced to puppet server containers

people actually fix 6+ year old stuff? :)

well, sometimes it still bugs people after 6+ years ;)

bastelfreak, it doesn't look like people are interested in ubuntu 22.04 ;)

don't get me started

since almost a decade we need to beg Puppet to provide releases shortly after each distro major release, what the hell

oh surprise, a distro made a major release. oh surprise, people want to use it

yeah

I suppose that's made worse by using a whole AIO install where you HAVE to use the Puppet provided packages

and the distro ones are bad because they're so old

Maybe packaging should be decoupled from releases

I checked and even Ubuntu lunar has 5.5.22 according to https://packages.ubuntu.com/lunar/puppet so it's just that nobody really works on it

it's universe 🤷

@Yury Bushmelev, on FreeBSD, well, most BSDs, it is.

I was tempted to update Puppet in EPEL 8 to Puppet 7, but that chose a unique layout that no other version uses (while Fedora and EPEL 9 are at least consistent with some others) so haven't done that yet

Ubuntu just uses the debian upstream from like 6 months before release or something like that, so I would hope that once the debian 7 packages (that someone I don't remember who) was working on is done it should get down to Ubuntu, but it probably could use a real group to manage it)

anarcat and others were, though I have rebuilt them for bullseye on https://ekohl.nl/debian/ to do some testing

the debian packaging work is progressing

we've got jruby back in, it was the last puzzle piece before being able to package puppetserver

we should be done by the time debian 12 / bookworm releases in a few months

as long as Puppet Agent is provided, I'm already more than happy

agreed, puppet-agent is much more important to me than puppetserver - mostly because I run puppetserver on a CentOS machine but puppet-agent on Debian

This message was deleted.

I've begun shifting to the pupperware containers just to avoid having to care about the packaging.....

bastelfreak: could you push the 5.4.0 for https://github.com/voxpupuli/modulesync_config/tags?

No rush, but would appreciate a review and/or feedback on https://github.com/voxpupuli/puppet-nginx/pull/1531 once everything passes. Tried to keep it compatible so there's not any breaking changes, and added a new test for each, but allowing for an alternate format on 2 types to allow option subdirectory depths for 2 options 🤞

No rush, but would appreciate a review and/or feedback on https://github.com/voxpupuli/puppet-nginx/pull/1531 once everything passes. Tried to keep it compatible so there's not any breaking changes, and added a new test for each, but allowing for an alternate format on 2 types to allow option subdirectory depths for 2 options 🤞

This seems to be stuck https://github.com/voxpupuli/puppet-logstash/actions/runs/3836415268/jobs/6530571542 Any idea how to kill it?

ewoud: sorry, pushed the missing tag