[Pkg-leofs-devel] Bug#837259: erlang-getopt: FTBFS: Uncaught error in rebar_core: {'EXIT',

[Lucas Nussbaum]

Source: erlang-getopt
Version: 0.8.2+dfsg-1
Severity: serious
Tags: stretch sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20160910 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --buildsystem=rebar --with rebar
>    dh_testdir -O--buildsystem=rebar
>    dh_auto_clean -O--buildsystem=rebar
> 	make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile clean
> clean
> rebar clean skip_deps=true -vv
> DEBUG: Consult config file "/<<BUILDDIR>>/erlang-getopt-0.8.2+dfsg/rebar.config"
> Uncaught error in rebar_core: {'EXIT',
>                                {undef,
>                                 [{crypto,start,[],[]},
>                                  {rebar,run_aux,2,
>                                   [{file,"src/rebar.erl"},{line,212}]},
>                                  {rebar,main,1,
>                                   [{file,"src/rebar.erl"},{line,58}]},
>                                  {escript,run,2,
>                                   [{file,"escript.erl"},{line,757}]},
>                                  {escript,start,1,
>                                   [{file,"escript.erl"},{line,277}]},
>                                  {init,start_em,1,[]},
>                                  {init,do_boot,3,[]}]}}
> /usr/share/dh-rebar/make/dh-rebar.Makefile:116: recipe for target 'clean' failed
> make[1]: *** [clean] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/09/10/erlang-getopt_0.8.2+dfsg-1_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.