ah nice

hey, i added a page for sponsoring on our page https://github.com/voxpupuli/voxpupuli.github.io/pull/292 input welcome :)

Have a bit of a chicken / egg situation with two PRs for puppet-rabbitmq. Would love some help if someone can spare some to get the pipelines at least somewhat un-blocked / un-broken. https://github.com/voxpupuli/puppet-rabbitmq/pull/928 and then the open modulesync PR (just tried re-generating that one; I think some of the modulesync failures will go away if we can get the tests passing for the other.

See the

puppet-rabbitmq

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

the alternative would, I guess, be to drop support for older OSes and not (yet) add support for the newer ones, but this doesn't seem ideal.

Some of the failing tests related to fqdn - seems like the Debian 9 / Ubuntu 18 images have the domain set to example.com, so that the fqdn is [hostname].example.com vs just bare [hostname]. This is I think part of the reason for the clustering failures anyway

Ok, I think I got https://github.com/voxpupuli/puppet-rabbitmq/pull/928 working... would be great if someone could re-review, since it's changed a lot since bastelfreak approved it. I will merge the two commits separately

Hey, I am new here and I have a few pullrequests open for the puppet-openssl module (one already got approved by bastelfreak; thanks!)

but the module still has some bigger problems :P especially since its only supporting puppet6 (which is EOL)

See the

puppet-openssl

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

my question would be: how is maintaining organized in voxpupuli? is there a dedicated maintainer for a module, or is everyone sort of responsible for everything? :D

"toll, ein anderer machts" ;-)

Zhenech: you're now the openssl maintainer

eh, zilchms ^

fffffffffff

ok

Zhenech: well you can maintain it too

zilchms, CI runs based on the setting in https://github.com/voxpupuli/puppet-openssl/blob/master/metadata.json#L67 - if you bump it and CI is still happy, you're lucky and can carry on

otherwise, yeah, you're now the maintainer ;)

wubwub i guess? :D

Zhenech, I can maintain it if you want. But I think I need to be able to merge pull requests, to do that Xd

that can be arranged, usually faster than you think :P

I feared that might be the case XD

Any idea on how to continue with https://github.com/sgnl05/sgnl05-sssd/issues/102 @sgnl05 seems to be unresponsive.

just fork it?

anyone ever seen an error log "Evaluation Error: Error while evaluating a '=>' expression, Use of a Ruby Integer outside of Puppet Integer max range, got '0x8000000000000000'"

lol, yes

your integer is too big :D

https://bugzilla.redhat.com/show_bug.cgi?id=2196825 has context if you're interested

the cause is the available_bytes fact from facter itself when using an 8 EiB filesystem …