I think the latest puppet-yum module has a design flaw. The assumption is made that

yum.repos.d

is collection of 'file' resources. In my experience, it's not the case, yumrepo doesn't add 'file' resource in catalog

bastelfreak: I won’t make the sync tomorrow :-( last minute meeting showed up

ibprobsbly wont make it as well, vacationing

me neither

we (sicura/simp) have a need for https://github.com/puppetlabs/beaker-google, so we're looking at resurrecting it. would it make sense to try to get that moved over to vox? (this will be news for @tvaughan 😁)

we (sicura/simp) have a need for https://github.com/puppetlabs/beaker-google, so we're looking at resurrecting it. would it make sense to try to get that moved over to vox? (this will be news for @tvaughan 😁)

I guess thats fine. I assune you want to maintain it a bit

we will definitely be putting some work into it...

Yaaas....I'll get my patch of betterness in there 😄

This message was deleted.

This message was deleted.

I mostly work on FreeBSD but also on Debian, no rvm/rbenv (I use the default version of Ruby from my OS), I just configure bundler to bundle to

~/.vendor

so that I can work as user and use a single directory for all these gems and just

bundle exec ...

everything.

I remember rvm being something really ugly, switched to rbenv at some point which was cleaner (just add a directory in your path), and then bundler was something that worked so I stop using this completly a lot of years ago

I remember rvm being something really ugly (creates aliases in your shell), switched to rbenv at some point which was cleaner (just add a directory in your path), and then bundler was something that worked so I stop using this completly a lot of years ago

I always feel uncomfortable running anything ruby because everything just downloads a gabillion gems and it's such an easy target for typosquatting (like most such systems)

Should just run rubydev stuff in a virtual machine and reset it every time I'm done :P

doesnt make that much of a difference if you if you download random stuff via apt or bundler :D

and for the gems; at least a huge amount of them is directly maintained by us or pupppetlabs

This message was deleted.

See the

thias-sysctl

module at https://forge.puppet.com/thias/sysctl?src=slack&channel=voxpupuli

There's a module thias/sysctl which isn't receiving any updates. I've tried to reach the module author on multiple ways, but I'm not getting any response (even if there's some activity on GitHub). Does it makes sense, to fork the module as voxpupuli or what's a good way in such a case? I'm happy to put some effort in, as I'm currently relying on some fork anyways and need to do some updates (forking the fork...).

we have forked modules in the past and I see https://github.com/thias/puppet-sysctl/issues/64 has been open for a while so IMHO it's a candidate for a fork

This message was deleted.

I did prefer to use https://github.com/voxpupuli/puppet-augeasproviders_sysctl

that's what we're using at this point as well

who was working on the webhook-go project replacing the old ruby webhook, I'm doing some testing with it and wanted to clarify if it supported multiple branches on the r10k pull, it looks like the patameter only supports 1

specifically the r10::default_branch param

r10k