On Fri, 2019-03-08 at 16:57 +0100, Timothée Floure wrote: > The issue seems to be specific to our environment (the Internet, > including > upstream, *seems* unaware of the issue): > * `rebar3 compile` works like a charm fetching dependencies from > the Internet > * `rebar3 bare compile -p $PATHS --separator :` fails with [0] > * This behavior can be reproduced with both our erlang-rebar3 > package and the > precompiled rebar3 published on github (under releases) > > Building a bootstrapped package for rebar3 3.7.x fixes the issue, > allowing to > build rebar3 3.7.x, 3.8.x and 3.9.x; > > I'm ways too tired to keep staring at my screen - I'm out for the day > ;-)
I don't really know Erlang well enough to understand the issue, but generally maybe a good first step might be to report the issue to the rebar project to get their take on it. Maybe they can make a new 3.9.z release that can be built offline with 3.6 for us? If that doesn't work out, we could ask FESCo for an exception to re- bootstrap it.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ erlang mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
