This repository has been archived by the owner on Dec 26, 2017. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 100
Vagrant doesn't use SemVer #97
Comments
SemVer allows prerelease version numbers, so that is valid. This is a solve issue. |
Yep, this is a solve issue. I'm going to close this and re-open it on Solve. |
tmatilai
added a commit
to tmatilai/vagrant-berkshelf
that referenced
this issue
Sep 30, 2013
`Solve::Constraint` doesn't support pre-release version numbers[1], so replace it with `Gem` classes while waiting for a fix. Fixes berkshelf#97 [1]: berkshelf#97
tmatilai
added a commit
to tmatilai/vagrant-berkshelf
that referenced
this issue
Sep 30, 2013
`Solve::Constraint` doesn't support pre-release version numbers[1], so replace it with `Gem` classes while waiting for a fix. Fixes berkshelf#97 [1]: berkshelf/solve#29
tmatilai
added a commit
to tmatilai/vagrant-berkshelf
that referenced
this issue
Dec 11, 2013
`Solve::Constraint` doesn't support pre-release version numbers[1], so replace it with `Gem` classes while waiting for a fix. Fixes berkshelf#97 [1]: berkshelf/solve#29
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
https://github.com/RiotGames/vagrant-berkshelf/blob/master/lib/berkshelf/vagrant/action/install.rb#L57 uses SemVer to check the running version of Vagrant.
Any 'dev' version e.g.
1.3.4.dev
won't work withvagrant-berkshelf
.Related: hashicorp/vagrant#2266
The text was updated successfully, but these errors were encountered: