Bug 2037932

Summary: Please branch and build elixir in epel9
Product: [Fedora] Fedora EPEL Reporter: Neil Hanlon <neil>
Component: elixirAssignee: Timothée Floure <timothee.floure>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: jeckersb, jochen, lemenkov, martin, puiterwijk, relrod, timothee.floure
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-03-25 21:51:58 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:

Description Neil Hanlon 2022-01-06 21:07:02 UTC
Please branch and build elixer in epel9

Comment 1 Neil Hanlon 2022-05-24 18:20:49 UTC
Will you be able to branch and build elixir in epel9?

Comment 2 Timothée Floure 2022-06-02 18:58:14 UTC
It's a bit hard than 'just building it for EPEL', since it needs building a bunch of dependent packages for EPEL9 as well. I do not currently have the bandwidth to do so: I don't see it happening in the foreseeable future unless someone else step up with this work (who I woudl gladly support). Another thing is that erlang packaging macro in Fedora/EPEL still depend on long-deprecated rebar2 (instead of rebar3) - it would be best to fix it before porting to EPEL.

Comment 3 Peter Lemenkov 2026-03-25 21:51:58 UTC
Elixir is now available for all EL9 derivatives (CentOS Stream 9, AlmaLinux 9, Rocky Linux 9, RHEL 9) via the CentOS Messaging SIG:

dnf install centos-release-messaging

This provides the full Erlang/OTP stack including Elixir. The centos-release-messaging package is available in the extras repository of AlmaLinux and Rocky Linux, so it works out of the box on all major EL9 distributions.

Building Elixir in EPEL would duplicate the Messaging SIG effort and create potential conflicts. Closing in favor of the SIG.