Bug ID: 1379898
Summary: rebar does not seem to build ejabberd, but does not
print any errors and returns exit code 0
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, filip(a)andresovi.net,
Created attachment 1205382
Description of problem:
I've been working on debugging ejabberd's build, and I think it might be a
problem in rebar. It looks like rebar is checking the dependencies and exiting
with code 0 with seemingly no errors, without building anything.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try to build ejabberd on Rawhide
The build fails, due to rebar not building any beam or app files.
Rebar should either build the files or print an error and return an exit code.
I am going to attach the full rebar output. I used my spec file to create a
failing build in ~/rpbbuild/BUILD/ejabberd-16.08 so that I would have all the
patches applied and dependencies installed. Then I ran the commands shown in
the attachment. Note that rebar exits after resolving the dependency
information, but does not seem to build any output, doesn't print errors, and
returns a 0 exit code.
The output does not show this, but earlier in this shell session I did run
these commands so that rebar would skip looking for the dependencies in the
You are receiving this mail because:
You are on the CC list for the bug.