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

... has invalid version ~> Version_1 or ~> Version_2 #11

Open
starbelly opened this issue Jul 1, 2023 · 2 comments
Open

... has invalid version ~> Version_1 or ~> Version_2 #11

starbelly opened this issue Jul 1, 2023 · 2 comments

Comments

@starbelly
Copy link
Owner

Originally reported by ulfa in Supersonido/rebar_mix#6

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.

@starbelly
Copy link
Owner Author

Confirmed. This, is due to rebar not supporting these type of constraints. This PR (draft) attempts to resolve this by migrating to verl in rebar3 : erlang/rebar3#2785

@filmor
Copy link
Contributor

filmor commented Oct 4, 2023

It was an attempt, but this stuff is really complicated :/

I'm trying it again now entirely independent of verl by first attempting to introduce a distinction between requirements and versions in rebar3.

/EDIT: And I think I already wrote this somewhere else: In my opinion, this is the single most critical issue for rebar3/elixir compatibility, having different resolution algorithms for deps and even incompatible requirement formats.

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