Description of problem: When running `rebar3 new app myapp`, no templates are found, so the app structure is not created and instead errors with "template not found." Version-Release number of selected component (if applicable): erlang-rebar3-3.14.3-3.fc35.src.rpm How reproducible: Always. Steps to Reproduce: 1. `sudo dnf -y install erlang-rebar3` 2. `rebar3 new app myapp` Actual results: Outputs "template not found." and does not create an application directory. Expected results: Creating the app structure under the 'myapp` directory. Additional info: This is appears to be the exact bug that reached EOL here: https://bugzilla.redhat.com/show_bug.cgi?id=1919729. The issue persists.
FEDORA-2022-a0bbde50cd has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a0bbde50cd
FEDORA-2022-a0bbde50cd has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-a0bbde50cd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a0bbde50cd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-a0bbde50cd has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
This is marked fixed but is not fully. Ran the following: ~ $ sudo dnf upgrade --advisory=FEDORA-2022-a0bbde50cd erlang-rebar3 Confirmed installed the new package: ~ $ sudo dnf info erlang-rebar3 Last metadata expiration check: 0:10:56 ago on Thu 17 Feb 2022 06:06:35 AM EST. Installed Packages Name : erlang-rebar3 Version : 3.18.0 Release : 2.fc35 Architecture : noarch Size : 1.3 M Source : erlang-rebar3-3.18.0-2.fc35.src.rpm Repository : @System From repo : updates Summary : Tool for working with Erlang projects URL : https://github.com/erlang/rebar3 License : ASL 2.0 and MIT Description : Rebar3 is an Erlang tool that makes it easy to create, develop, and release : Erlang libraries, applications, and systems in a repeatable manner. The error persists: ~ $ rebar3 new app foobar template not found. However, I see there are now templates in the package: ~ $ dnf repoquery -l erlang-rebar3 | grep templates Last metadata expiration check: 0:25:31 ago on Thu 17 Feb 2022 06:13:50 AM EST. /usr/share/erlang/lib/rebar3-3.18.0/priv/templates /usr/share/erlang/lib/rebar3-3.18.0/priv/templates/LICENSE /usr/share/erlang/lib/rebar3-3.18.0/priv/templates/Makefile /usr/share/erlang/lib/rebar3-3.18.0/priv/templates/README.md /usr/share/erlang/lib/rebar3-3.18.0/priv/templates/app.erl /usr/share/erlang/lib/rebar3-3.18.0/priv/templates/app.template /usr/share/erlang/lib/rebar3-3.18.0/priv/templates/app_rebar.config ... According to Rebar3 documentation, it by default looks for templates in $HOME/.config/rebar3/templates. After symlinking this directory to /usr/share/erlang/lib/rebar3-3.18.0/priv/templates, things seem to work. ~ $ ln -s /usr/share/erlang/lib/rebar3-3.18.0/priv/templates ~/.config/rebar3/template ~ $ rebar3 new app (custom): Complete OTP Application structure. cmake (custom): Standalone Makefile for building C/C++ in c_src escript (custom): Complete escriptized application structure lib (custom): Complete OTP Library application (no processes) structure plugin (custom): Rebar3 plugin project structure release (custom): OTP Release structure for executable programs umbrella (custom): OTP structure for executable programs (alias of 'release' template) However the need to do this is non-obvious and an installation of the package as-is still doesn't allow usage of templates. Should this package automatically create this symlink? It is non-obvious from Rebar3 documentation if it is possible to control the template path via environment variable or otherwise.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.