-
-
Notifications
You must be signed in to change notification settings - Fork 245
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
Upgrade from 4.x to 5.x, Downgrade from 5.x to 4.x #197
Comments
|
👍 @fstr! |
|
I was working with the 0.8.0 release from puppetlabs, you should publish a new release there! But the problem seems to persist/be slightly different for the latest 1.3.0 release. When I change the With the change I proposed providing a certain version, the install fails because of the missing apt-get update. The best fix I found so far, is doing a Example: I'll try to provide a PR later. |
@fstr puppetlabs/nodejs has been moved to voxpupuli (on the forge this is the /puppet namespace) |
…ate the sources.list Until now only the value 'present' caused a sources.list update. Now it's possible to also provide a certain version or other values like 'latest' Only if 'absent' is provided explicitly, the nodejs package will be purged.
…ackage Until now when switching between versions (e.g. 4.x to 5.x) the sources.list was updated, but the command apt-get update was never executed before trying to install a new package This patch requires an explicit call to apt-get update before each package installation, to make sure the latest updates to the sources.list are used
…ackage Until now when switching between versions (e.g. 4.x to 5.x) the sources.list was updated, but the command apt-get update was never executed before trying to install a new package This patch requires an explicit call to apt-get update before each package installation, to make sure the latest updates to the sources.list are used
Making it possible to provide concrete nodejs versions to force upgrade/downgrade (#197)
|
Proposed fix merged in #198 |
…ate the sources.list Until now only the value 'present' caused a sources.list update. Now it's possible to also provide a certain version or other values like 'latest' Only if 'absent' is provided explicitly, the nodejs package will be purged.
Making it possible to provide concrete nodejs versions to force upgrade/downgrade (voxpupuli#197)
Just changing the
repo_url_suffixfromnode_4.xtonode_5.xand set ensure topresentorlatestdoesn't do any changes.Version 4.x will still be installed, since it fulfills the
presentrequirement.A way to force a new version is to set a certain version.
For an upgrade:
latestdoes not work for a downgrade though, so for a downgrade you have to do something like this:Sadly, the apt.pp file only updates the sources if the nodejs_package_ensure is set to
presentMaybe I got it all wrong and there's another way to upgrade/downgrade major versions. Otherwise I'd write a PR.
So I propose a change
The text was updated successfully, but these errors were encountered: