Skip to content
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

Wrong package installed with default repo on Ubuntu 16.04 LTS #171

Open
AlexeyDemidov opened this issue Apr 30, 2017 · 3 comments
Open

Wrong package installed with default repo on Ubuntu 16.04 LTS #171

AlexeyDemidov opened this issue Apr 30, 2017 · 3 comments
Labels
Priority: Low Is a nice to have, not an essential

Comments

@AlexeyDemidov
Copy link

When installing from packages on Ubuntu 16.04 LTS with default repo we get nodejs-4.2.6~dfsg-1ubuntu4.1 package from Ubuntu repo instead of deb.nodesource.com. The apt-cache policy nodejs output:

nodejs:
  Installed: (none)
  Candidate: 4.2.6~dfsg-1ubuntu4.1
  Version table:
     4.2.6~dfsg-1ubuntu4.1 500
        500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages
     4.2.6~dfsg-1ubuntu4 500
        500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
     0.10.46-1nodesource1~xenial1 500
        500 https://deb.nodesource.com/node xenial/main amd64 Packages

The fix is to set node['nodejs']['repo'] = 'https://deb.nodesource.com/node_6.x' (default repo is https://deb.nodesource.com/node)

@espoelstra
Copy link

An easy way to correct this is to specify a major version in the attributes/default.rb like default['nodejs']['version'] = '6' which will get interpolated into the URL and allow installing the intended version of NodeJS.

@github-actions
Copy link

Marking stale due to inactivity. Remove stale label or comment or this will be closed in 7 days. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help! Thanks, Sous-Chefs.

@github-actions github-actions bot added the Stale label Sep 30, 2020
@xorimabot xorimabot removed the Stale label Sep 30, 2020
@MarkGibbons MarkGibbons added the Priority: Low Is a nice to have, not an essential label Oct 3, 2020
@MarkGibbons
Copy link
Member

Adding default repository as this cookbook does in the repo recipe seems to cause this issue. I believe the cookbook is working as designed ( the design may be bad but that's a separate issue.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Low Is a nice to have, not an essential
Projects
None yet
Development

No branches or pull requests

4 participants