-
-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using third party repo on Debian (11) does not work correctly #475
Comments
Duplicate of #452 |
The outcome is markedly differnet though, in the case of #452 Setting
|
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
Starting from a machine which has no node or npm installed at all.
On the first Puppet run when adding the nodejs class to the machine, the nodesource apt repo configuration is added. Node is installed from Debian sources (not the 3rd party repo) along with a zillion node-* support packages. The
npm
package is pulled in by this, I believe, then removed by the Puppet module at the end of the run.I run
apt-get upgrade
to install available updates. This, now using the nodesource apt repo, will remove all packages pulled in earlier and replace them by a singlenodejs
package in version 16, as requested.On every Puppet run after this upgrade happened, the module now tries to install the
npm
package from Debian's repositories, which conflicts with the nodesourcenodejs
package (which already contains its own npm, it is not a separate package). The Puppet run fails due to this error.Setting
npm_package_ensure
toabsent
makes no difference to this behaviour.What behaviour did you expect instead
Installation of node v16 (preferrably immediately), but more importantly, non-failing Puppet runs after this has happened.
Output log
The text was updated successfully, but these errors were encountered: