Table of Contents
- Quickstart
- EL9
- EL8
- EL7
- What is Extra Packages for Enterprise Linux (or EPEL)?
- What is EPEL-Next?
- What packages and versions are available in EPEL?
- END OF LIFE RELEASES
- How can I use these extra packages?
- Can I rely on these packages?
- History and background of the project
- How can I contribute?
- Communicating with the EPEL SIG
Welcome to the home of the EPEL Special Interest Group.
Quickstart
We offer release packages containing our repository configuration files and public package signing keys.Use the version that corresponds to the major version of your operating system.
If you are using CentOS Stream, we also recommend installing the corresponding epel-next-release package.
For convenience some distributions include these release packages in their default repositories,allowing you to install them by name without the full URL.
Some EPEL packages depend on packages from repositories that are not enabled by default.Take note of the additional repositories being enabled in the following instructions.
EL9
CentOS Stream 9
dnf config-manager --set-enabled crbdnf install epel-release epel-next-release
RHEL 9
subscription-manager repos --enable codeready-builder-for-rhel-9-$(arch)-rpmsdnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
AlmaLinux 9, Rocky Linux 9
dnf config-manager --set-enabled crbdnf install epel-release
EL8
CentOS Stream 8
dnf config-manager --set-enabled powertoolsdnf install epel-release epel-next-release
RHEL 8
subscription-manager repos --enable codeready-builder-for-rhel-8-$(arch)-rpmsdnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
AlmaLinux 8, Rocky Linux 8
dnf config-manager --set-enabled powertoolsdnf install epel-release
EL7
RHEL 7
subscription-manager repos --enable rhel-*-optional-rpms \ --enable rhel-*-extras-rpms \ --enable rhel-ha-for-rhel-*-server-rpmsyum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
CentOS 7
yum install epel-release
What is Extra Packages for Enterprise Linux (or EPEL)?
Extra Packages for Enterprise Linux (or EPEL) is a Fedora SpecialInterest Group that creates, maintains, and manages a high quality setof additional packages for Enterprise Linux, including, but not limitedto, Red Hat Enterprise Linux (RHEL),CentOS, Scientific Linux (SL), Oracle Linux (OL), AlmaLinux (AL) and Rocky Linux (RL).
EPEL packages are usually based on their Fedora counterparts and willnever conflict with or replace packages in the base Enterprise Linuxdistributions. EPEL uses much of the same infrastructure as Fedora,including buildsystem, Bugzilla instance, updates manager, mirrormanager and more.
Learn more about EPEL in the following pages:
EPEL FAQ
About EPEL
EPEL Guidelines and Policies
What is EPEL-Next?
EPEL packages are built against RHEL. EPEL Next packages are built against CentOS Stream.
EPEL-Next is not a complete rebuild of all the EPEL packages, but only those packages that need to be rebuilt to install on CentOS Stream. The EPEL-Next repo is meant to be layered on top of the regular EPEL repository.
Learn more about EPEL-Next on the following page:
EPEL Next
What packages and versions are available in EPEL?
Since EPEL is part of the Fedora project, you can search the available packages in theFedora Packages web app.This provides an overview of available versions across various EPEL branches.If you find a package that is not yet available in the EPEL branch you would like it to be,please follow this guide to request it.
Alternately, you can browse the repo files directly:
You can also browse these same directories on any of ourmirrors.
END OF LIFE RELEASES
THESE ARE NO LONGER SUPPORTED
| Due to major security changes in SSL in the last 10 years, olderreleases may not be able to directly point to these releases. As of2021-01-22, EPEL-5 and 4 systems do not have the newer TLS 1.2 algorithmsthat Internet servers are required to use for security reasons. The bestmethod for working with these is to have a newer system mirror theentire archive and then for your systems to point to that mirror. |
How can I use these extra packages?
EPEL has an 'epel-release' package that includes GPG keys for packagesigning and repository information. Installing this package for yourEnterprise Linux version should allow you to use normal tools such asyum to install packages and their dependencies. By default the stableEPEL repo is enabled, there is also a 'epel-testing'repository that contains packages that are not yet deemed stable.
NOTE for RHN users: You need to also enable the 'optional' repositoryto use EPEL packages as they depend on packages in that repository. Thiscan be done by enabling the RHEL optionalsubchannel for RHN-Classic.For certificate-based subscriptions seeRedHat Subscription Management Guide.
NOTE for RHEL 7 users with certificate subscriptions: EPEL 7 packagesassume that the 'optional' repository (rhel-7-server-optional-rpms forservers) and the 'extras' repository (rhel-7-server-extras-rpms forservers) are enabled. You can do this with:
subscription-manager repos --enable rhel-7-server-optional-rpms --enable rhel-7-server-extras-rpms
NOTE for RHEL 8 users with certificate subscriptions: EPEL packagesassume that the 'codeready-builder' repository is enabled. You can dothis with:
subscription-manager repos --enable "codeready-builder-for-rhel-8-$(arch)-rpms"
NOTE for CentOS 8 and CentOS Stream 8 users: EPEL packages assume that the 'powertools'repository is enabled. You can do this with:
dnf config-manager --set-enabled powertools
NOTE for CentOS users: You can install EPEL by running yum installepel-release. The package is included in the CentOS Extras repository,enabled by default.
You can verify these packages and their keys from the Fedora project’skeys page: https://fedoraproject.org/keys
Can I rely on these packages?
The EPEL project strives to provide packages with both high quality andstability. However, EPEL is maintained by a community of people whogenerally volunteer their time and no commercial support is provided. Itis the nature of such a project that packages will come and go from theEPEL repositories over the course of a single release. In addition, itis possible that occasionally an incompatible update will be releasedsuch that administrator action is required. By policy these areannounced in advance in order to give administrators time to test andprovide suggestions.
It is strongly recommended that if you make use of EPEL, and especially if yourely upon it, that you subscribe to theepel-announcelist. Traffic on this list is kept to a minimum needed to notify administratorsof important updates.
History and background of the project
The EPEL project was born when Fedora maintainers realized that the sameinfrastructure that builds and maintains packages for Fedora would begreat to also maintain add on packages for Enterprise Linux. Much of theearly need was driven by what Fedora infrastructure needed on the RHELmachines that built and maintained Fedora. From there things have grownto a large collection of varied packages. Seeour history and Philosophy page formore information.
How can I contribute?
The EPEL SIG is always looking for interested folks to help out. Wealways need package maintainers, QA/testers, bug triagers anddocumentation writers. Please see our Joining EPELpage for more information on how to join the SIG.
Communicating with the EPEL SIG
There are many ways to communicate with the EPEL SIG and its members:
The #epel IRC channel onLibera Chat offers real-timesupport for EPEL users and developers.This channel is bridged to epel:fedoraproject.org on Matrix.
The epel-develmailing list is for general developer and SIG discussion.Historic archives are available.
Theepel-announcemailing list is a low volume mailing list for only important announcements.
Theepel-package-announcemailing list is a list that gets information about package updates as theyhappen in the stable repository.
If you find a bug in a EPEL maintained package, please report it tohttps://bugzilla.redhat.com/under the "Fedora EPEL" product.
Infrastructure issues (mirrors, repos, etc.) should be reported toFedora releng.
The EPEL SIG meets on Wednesday every week in the#fedora-meetingIRC channel at 21:00 UTC.This channel is bridged to #meeting:fedoraproject.org on Matrix.Please check the time on theepel calendar; sometimesit can change or a meeting can be skipped. Feel free to join us! Logs ofpast meetings can be viewed inmeetbot.
The EPEL Steering Committee hasmonthlyoffice hours for the EPEL project.
Want to help? Learn how to contribute to Fedora Docs.
