Kenyon Ralph
Kenyon Ralph
The documentation has the existing address, which still works: https://pip.pypa.io/en/stable/installing/#installing-with-get-pip-py Where are you seeing that the address has been updated?
> Same with ubuntu focal (20.04). Is there a workaround to allow us to specify python3-pip? Otherwise a lot of this module is unuseable on these (very popular) platforms. @alchemyconsulting...
> Because config files have been managed by hand until now, inconsistencies and errors the parameter naming (small vs. capital letters, type-errors, double entries) happened all over the place, so...
IMO it's best to avoid non-distribution package repos if possible. I use this module like this on Debian: ```puppet class { 'nodejs': manage_package_repo => false, npm_package_ensure => present, } ````
Seems like something weird about npm in docker: it wants to use `/usr/etc/npmrc` instead of `/etc/npmrc`, but of course `/usr/etc` doesn't exist.
This warning seems to happen for any puppetserver command. https://tickets.puppetlabs.com/browse/SERVER-2761
Same problem in the README.md of each hercules-team repository.
Rebasing or cherry-picking the commits would maintain the original commit authors.