well.. https://github.com/voxpupuli/beaker-lima <- let me know if anyone would like to try it on Mac M1/M2 🙂

should be usable on Linux too (as Lima is available for Linux)

I’d say this is my biggest Ruby-based project ever 🙂

though.. maybe tasks in puppet-lima are larger..

https://github.com/voxpupuli/puppet-systemd/actions/runs/4831254455/jobs/8608450517?pr=342 I think we broke our CI for all modules that use the pidfile workaround

ah no that's without the pidfile, mhm

ah that's because of Fedora 36 in the metadata.json

ahhhhh

m(

derp

we will need https://github.com/voxpupuli/puppet_metadata/pull/87 and a new modulesync to fix CI

I added a lot of reviewers to this PR, because I wanted to move forward to issue #87 https://github.com/voxpupuli/puppet-nomad/pull/85

Is there any way voxpupuli could do a 'takeover' of abrader/abrader-gms or more specifically, the unmerged pull request from bjvrielink's fork? I have been trying for more than a year to reach Andrew Brader and bjvrielink isn't responding, either. The pull request need to be merged into abrader-gms in order to make R10k work properly. If that's not possible, can the README.md be updated to reflect the current 'good' location to the gms project?

do you want to maintain it in the vox pupuli namespace? or does your company want to pay someone for a migration and/or maintenance?

in case upstream doesnt respond to a migration request, we could probaby copy the relevant code into https://github.com/voxpupuli/puppet-git_resource

I am completely unqualified to maintain it as I know nothing about Ruby. The owner of the project has not updated the project in years. There is a years-old pull request that needs to be merged in order for gitlab integration to work.

I don't know how it works but it makes sense that the code base plus the pull request be migrated over to [eg] voxpupuli/gms.

if the original author responds they could migrate the whole repo to us

At the moment I dont have more time to maintain more modules in my free time

I've been trying for more than a year to contact him. Even Gary Larizza was unable to contact Andrew Brader. I'm happy to try to maintain the module but I have no experience with Ruby. However, the only things that really need to happen are migrating the code, accepting the pull request and modifying the r10k readme.md file to reflect the new location for the gms project. I'm happy to do that.

At bare minimum: https://github.com/voxpupuli/puppet-r10k/pull/591

@Brian Schonecker can you please rebase? I fixed the CI errors yesterday

#593 Sorry, I accidentally closed my original pull request.

Can I get a review on https://github.com/voxpupuli/facterdb/pull/272?

please don't expect that I read the json for all those files 😄

I tried to diff against the 4.2 version and make sure that the changes looked sane