Bug 1748545

Summary:	undefined function rebar:main/1
Product:	[Fedora] Fedora	Reporter:	Randy Barlow <rbarlow>
Component:	erlang-rebar	Assignee:	Peter Lemenkov <lemenkov>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	filip, jeckersb, lemenkov, redhat, votava
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	erlang-rebar-2.6.4-13.fc31	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-19 01:34:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1672916, 1735184, 1735185, 1735186, 1735189, 1742452, 1742453, 1742454, 1742455, 1742456, 1742457, 1742460, 1742461, 1742462, 1742463, 1742469, 1742472, 1742538, 1748530, 1753074, 1755153, 1766472, 1768137

Description Randy Barlow 2019-09-03 20:00:26 UTC

Description of problem:
Rebar seems to be broken on Rawhide:

$ rebar --version
escript: exception error: undefined function rebar:main/1
  in function  erl_eval:local_func/6 (erl_eval.erl, line 567)
  in call from escript:interpret/4 (escript.erl, line 788)
  in call from escript:start/1 (escript.erl, line 277)
  in call from init:start_em/1 
  in call from init:do_boot/3

I see a similar traceback when building erlang-p1_utils, so I assume all of my erlang packages are broken:

+ /usr/bin/rebar compile skip_deps=true -vv
escript: exception error: undefined function rebar:main/1
  in function  erl_eval:local_func/6 (erl_eval.erl, line 567)
  in call from escript:interpret/4 (escript.erl, line 788)
  in call from escript:start/1 (escript.erl, line 277)
  in call from init:start_em/1 
  in call from init:do_boot/3


Oddly, it fails in a different way in Koji:

https://kojipkgs.fedoraproject.org//work/tasks/4330/37444330/build.log


Version-Release number of selected component (if applicable):
erlang-rebar-2.6.4-10.fc31.noarch

Comment 1 Randy Barlow 2019-09-30 14:19:01 UTC

This affects Fedora 31 as well. For example, erlang-yaml will not build on F31:

https://koji.fedoraproject.org/koji/taskinfo?taskID=37967586

Comment 2 Fedora Update System 2019-11-09 00:43:48 UTC

FEDORA-2019-b35d5a8af6 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-b35d5a8af6

Comment 3 Fedora Update System 2019-11-09 23:21:13 UTC

erlang-rebar-2.6.4-12.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-b35d5a8af6

Comment 4 Fedora Update System 2019-11-11 01:38:24 UTC

erlang-eflame-0-0.15.gita085181.fc31, erlang-getopt-1.0.1-7.fc31, erlang-gettext-2.1.0-0.21.20170123git2bcba56.fc31, erlang-meck-0.8.13-4.fc31, erlang-mustache-0.1.1-13.fc31, erlang-neotoma-1.7.4-10.fc31, erlang-protobuffs-0.9.1-4.fc31, erlang-rebar-2.6.4-13.fc31, erlang-triq-1.3.0-3.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-dff59c85ae

Comment 5 Fedora Update System 2019-11-19 01:34:43 UTC

erlang-eflame-0-0.15.gita085181.fc31, erlang-getopt-1.0.1-7.fc31, erlang-gettext-2.1.0-0.21.20170123git2bcba56.fc31, erlang-meck-0.8.13-4.fc31, erlang-mustache-0.1.1-13.fc31, erlang-neotoma-1.7.4-10.fc31, erlang-protobuffs-0.9.1-4.fc31, erlang-rebar-2.6.4-13.fc31, erlang-triq-1.3.0-3.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.