-
Notifications
You must be signed in to change notification settings - Fork 20
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
... has invalid version ~> Version_1 or ~> Version_2 #6
Comments
Afraid that is the case, yes. For now you could try adding tzdata to your rebar.config list of dependencies too, then it might ignore the version requirement it can't handle. |
Hi, this doesn't work, because rebar3 always checks the version of the dependency. |
Damn, that is right, it will parse the version so it can print a warning that it is in conflict. Maybe a quick fix is to not care if it can't parse the version if the dep isn't actually going to be used. Like in this case if you have |
+1 Added
|
We'll have a new release of rebar3 soon that can handle these versions. |
Sorry, I forgot that the PR to fix this was actually reverted because of issues it caused erlang/rebar3#2486 |
I also meet the issue "Dep decimal has invalid version ~> 1.0 or ~> 2.0" when I am using rebar3 to download the elixir deps {protobuf, "0.10.0"} related info: |
You might at least want to try a newer Rebar3, we'Re up to 3.20. |
@ferd I update to rebar3 : rebar 3.17.0 on Erlang/OTP 22 Erts 10.7.2, still have the problem "Dep decimal has invalid version ~> 1.0 or ~> 2.0" |
Can you try the latest, 3.20.0? How are you installing rebar3? You can download an escript from https://www.rebar3.org/ |
@tsloughter installed from source code, also have issue |
Hi,
I am trying to use rebar3_mix, but when ich declare a dependency like
{timex, "~> 3.5"} rebar3 tries to download the dependencies from timex.
But the dependency of the timex package tzdata is declared in the mix.exs as {:tzdata, "~> 0.1.8 or ~> 0.5"} and I think rebar3 can't manage this.
The text was updated successfully, but these errors were encountered: