Bug 2037932 - Please branch and build elixir in epel9
Summary: Please branch and build elixir in epel9
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: elixir
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Timothée Floure
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-06 21:07 UTC by Neil Hanlon
Modified: 2026-03-25 21:51 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-03-25 21:51:58 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.