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

vagrant up command fails for openstreetmap-website #1402

Closed
IOOI-SqAR opened this issue Jan 3, 2017 · 3 comments
Closed

vagrant up command fails for openstreetmap-website #1402

IOOI-SqAR opened this issue Jan 3, 2017 · 3 comments

Comments

@IOOI-SqAR
Copy link
Contributor

When trying to follow the instructions given on https://github.com/openstreetmap/openstreetmap-website/blob/master/VAGRANT.md the vagrant up command fails like this:

==> default: Gem::InstallError: nokogiri requires Ruby version >= 2.1.0.
==> default: An error occurred while installing nokogiri (1.7.0), and Bundler cannot
==> default: continue.
==> default: Make sure that gem install nokogiri -v '1.7.0' succeeds before bundling.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

when I look further up in the vagrant output I can see that ruby2.0 (2.0.0.484-1ubuntu2.2) was installed before. I attached the full vagrant output:
openstreetmap-website vagrant up.0.log.txt

@tomhughes
Copy link
Member

Well as it says, you need ruby 2.1 not 2.0.

@tomhughes
Copy link
Member

I guess this probably needs the Vagrant file changing to a new image but I know nothing about the vagrant stuff.

@tomhughes tomhughes reopened this Jan 3, 2017
harry-wood added a commit to harry-wood/openstreetmap-website that referenced this issue Jan 3, 2017
change dependancies. nokogiri requires a later ruby now as pointed out here: openstreetmap#1402 ruby2.0->ruby 2.3 ...which then entails a later ubuntu if we're installing from packages.
@IOOI-SqAR
Copy link
Contributor Author

This now works as expected!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants