Romain Tartière

Yes: https://github.com/voxpupuli/puppet-mcollective/blob/a01131ba9688b5a4f64e4bad1ca742ccab6cd312/metadata.json#L14-L18 I think we should deprecate this voxpupuli module: MCollective was removed from Puppet, and the successor of MCollective, Choria, has it's own up-to-date modules to manage all components:...

No strong opinion about a new release first: this is part of some yak shaving :wink:

I don't see `nodejs-.rpm` (only `nodejs--.rpm`) on https://mirror.aarnet.edu.au/pub/epel/7/x86_64/Packages/n/ but see it on https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/6/x86_64/Packages/n/ so maybe yes :shrug: I guess we just have to axe it in a new breaking change...

@root-expert The 0.3.1 tag was probably a mistake ;-) I tried to fix the CentOS 7 failure in #453 but no luck so far :sob: If you have an idea…

I think it rings a bell: I do have this hack in `~/bin/vagrant` (before anything else in my `$PATH`) so that `vagrant` when run from a Ruby bundle ignore this...

I am wondering if the CI failures are relevant… Like `volume-1:C:\volume_1` being escaped as `volume-1:C:\\volume_1`… Not sure about how to check this…

@neomilium @chelnak I added a commit that seems to help… but escaping on windows is total nonsense and I am sure of nothing :scream: Some windows node pass, the one...

Last CI failures seems to be caused by inaccessible windows test nodes. I think this is ready for review.

@neomilium have you had a chance to see if the issue you originally tried to fix with this PR is indeed fixed with all these changes?

> @smortex @chelnak @bastelfreak - why has stdlib been raised to min v8.2.0 in the pull request? That is very high and will have breaking impact when combined with a...