Closed VitorTrin closed 1 year ago
Hello Victor.
Can you please check if when you fetch using {:erlkaf, "~> 2.1.0"}
you have rebar.config.script
in the packet ?
This file shouldn't be there... I have no explanation how arrived in the packet..
Hmm.. I have no clue to what rebar.config.script makes reference.. because mine has less than 22 lines.. and also I don't see it included into the packet..
Have you tried to update to last rebar3 ?
rebar3 --version
gives me rebar 3.15.2 on Erlang/OTP 25 Erts 13.1.3
and surprisingly, no the file does not appear to be in the packet. This line 22 thing smells like a macro at work that expands the file
It's probably https://github.com/fogfish/esq/issues/20
You are totally right ! But I don't see how can I fix this... I have no permissions on that library to update the hex package..
Silviu
@VitorTrin can you try {:erlkaf, "~> 2.1.1"}
. I just published it.
Silviu
I published {:erlkaf, "~> 2.1.2"}
as another problem with esq appeared.
Already received confirmation from another user that problem is solved.
When I use hex and I add a dependency to the latest release like this
fetching the deps results in the following error
This does not happen if we add the dependency directly from the github like this:
even though no changes happened to rebar config in the master since the last release