puppet-nodejs
puppet-nodejs copied to clipboard
voxpupuli
modulesync 5.3.0
@smortex looks like CentOS has some package conflicts. Is nodejs still supported there / did we setup the wrong repo / is epel broken maybe?
I don't see nodejs-<version>.rpm (only nodejs-<module>-<version>.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 PR.
Hey @sircubbi , do you have any ideas why the tests on CentOS 7 do not pass?
Hey @sircubbi , do you have any ideas why the tests on CentOS 7 do not pass?
Hmmm, nothing really catches my eye. Seems like some timeout while still setting up the docker-environment, but no specific cause I fear.
@sircubbi nownthe CI finally failed "properly", adter several docker-related issues. could you take a look again?
@sircubbi nownthe CI finally failed "properly", adter several docker-related issues. could you take a look again?
It seems that /usr/bin/npm is not found. If you pull nodejs from EPEL you would also need to install the npm-Package from epel too (when using nodesource that is not necessary, since the npm-Command is already provided by the base-Package).
I'll work on the EPEL failures. I can clean up the commit log once the code is good and the tests pass.
This PR contains non modulesync changes:
- Drop support for Debian 9, Ubuntu 16.04 and 18.04, FreeBSD 11 (EOL) (breaking)
- Add Puppet 8 support (feature)
- Add support for RHEL 9 based distros (feature)
How do I teach GHC that…
Yeah, there were pull requests closed for those, so not sure why GHC didn't include them.