[Pkg-erlang-devel] Bug#837234: Bug#837234: rebar: FTBFS: Uncaught error in rebar_core: {'EXIT',

[Sergei Golovan]

Hi!

On Sat, Sep 10, 2016 at 11:46 AM, Sergei Golovan <sgolovan at nes.ru> wrote:
> Hi!
>
> On Sat, Sep 10, 2016 at 10:26 AM, Lucas Nussbaum <lucas at debian.org> wrote:
>>
>> During a rebuild of all packages in sid, your package failed to build on
>> amd64.
>>
>>> Uncaught error in rebar_core: {'EXIT',
>>>                                {undef,
>>>                                 [{crypto,start,[],[]},
>
> The problem is that in the newer Erlang erlang-tools no longer pulls
> out the erlang-crypto package (it depended on erlang-crypto implicitly
> via erlang-inets and then erlang-ssl). So, erlang-crypto must be added
> to the build dependencies list explicitly now.

Also, erlang-crypto has to be added to the rebar dependencies list.
Otherwise, rebar won't start.

Moreover, looking through the rebar sources I've found quite a few
modules it uses directly, which packages can be added to the
dependencies list as well. The full list is:
erlang-asn1 (used in rebar_asn1_compiler only)
erlang-base
erlang-crypto
erlang-dialyzer (used in rebar_dialyzer.erl only)
erlang-diameter (used in rebar_dia_compiler.erl only)
erlang-edoc (used in rebar_edoc.erl only)
erlang-eunit (used in rebar_eunit.erl only)
erlang-reltool (used in rebar_reltool.erl only)
erlang-snmp (used in rebar_erlc_compiler.er only)l
erlang-syntax-tools (used in rebar_erlc_compiler.erl only)
erlang-tools

And finally, a few files mention some external modules (I guess they
are optional):
abnfc (used in rebar_abnfc_compiler.erl)
eflame (used in rebar.erl)
erlydtl (used in rebar_erlydtl_compiler.erl)
gpb_compile (used in rebar_proto_gpb_compiler.erl)
lfe_comp (used in rebar_lfe_compiler.erl)
neotoma (used in rebar_neotoma_compiler.erl)
protobuffs_compile (used in rebar_protobuffs_compiler.erl)

Hope that helps fixing the rebar dependencies.

Cheers!
-- 
Sergei Golovan