-
Notifications
You must be signed in to change notification settings - Fork 312
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
Versions not found if Major.Minor.Patch version is not specified #156
Comments
This is one of the most common issues I get emailed about from customers at gigalixir. @HashNuke I don't mind taking a stab at this if you think this is something you would be willing to merge. I can see how some people might not like their version "altered" automatically. One thing I can do right now, though, is improve the error message when a version isn't supported. What do you think? Right now, it says something like this
Perhaps something more useful like
What do you think? |
@jesseshieh I can't think of a single reason that someone who specified only a major / major.minor version would be mad that it used the latest patch when an exact match to their query doesn't exist |
this should definitely still fail if they specify a full semver and it's not found |
@jesseshieh That would be nice. Would be happy to merge a PR. |
I'm getting a very similar error message, but it doesn't matter what OTP version I'm trying to install:
can this be related, or should I open another ticket? I tried various versions listed here https://github.com/HashNuke/heroku-buildpack-elixir-otp-builds/blob/master/otp-versions |
This can happen if there was basically any kind of error downloading the file. I just tried it manually at https://s3.amazonaws.com/heroku-buildpack-elixir/erlang/cedar-14/OTP-21.3.tar.gz and it seemed to work. Is it still happening for you or was it a transient issue? Did you get this error from Heroku or Gigalixir? |
I got it from heroku, and downloading manually did work for me too. I'll try later today, maybe it was a hiccup with heroku. |
if you specify OTP 22.0 for instance, instead of using versioning to pull the closest match, the build fails.
If only a
Major
version or only aMajor
andMinor
version are specified, and an exact match isn't found, the build should use the most up-to-date version for thatMajor.Minor
combinationIt was really surprising that symversioning isn't followed in the absence of an exact match, and instead the build just fails. If a Patch version was specified, and not found, THEN it should fail
The text was updated successfully, but these errors were encountered: