If there is any simple enough explanation what are you trying to do :) as I never used the webhook yet

ewoud: Something is wrong on the Internet. Could you fix the typo in the the description of https://github.com/theforeman/puppet-certs It's hurting my eyes! 🙂

ewoud: Something is wrong on the Internet. Could you fix the typo in the the description of https://github.com/theforeman/puppet-certs It's hurting my eyes! 🙂

.

and another one

https://github.com/voxpupuli/puppet-augeasproviders_base/pull/5 now isn't pretty, but at least green

nice

if aomeone wants to take a look at augeasproviders_sysctl, that would be awesome

and augeasproviders_mounttab 😎

Coffee coffee

FriedBob: o/

How goes?

good good! and you?

Not too bad overall.

\o/

hi all i spoke with dalen about migarting puppet-dnsquery over to voxpupuli, i dont think they seem happy to do so and have gave me some permissions allthough not enough (https://github.com/dalen/puppet-dnsquery/issues/115). im happy to do the work to add modsync etc to get the modules into voxpupil shape and maitain it going foward. can i just get them to trafser it directly to voxpupil and ill pick

it up from there? or is there a better process to ...

... follow, im not sure they would be to inclined to do much work them self

*i think they seem happy to do so

scratch that they are happy to do so :)

jbond: do you want to maintain it? In that case we can probably move it to vox pupuli

bastelfreak: yes im happy to maintain it, they have also said they are happy to send the others over. im familure with puppetdbquery so can take that but less so with the others. if your happy ill ask them to just send them over and ill pick up the work to clean them up etc

maybe lets start with dnsquery first

ok sounds good to me cheers

jbond: after the migration we can go through https://voxpupuli.org/docs/migrate_module/

bastelfreak: ack thanks although it may need some clean up first, its currently listed as only supporting puppet 5.5, not sure if oyu would prefer that tidy up before or after its fully onboarded?

we probably just need to add the new puppet version to metadata.json

and we have to do that before/during the initial modulesync. because puppet 5 means ruby 2.3 ? and that doesnt work anymore with our gems

yes the Gemfile is also missing sync which caused an issue

only minor stuff