How to use Extra Packages for Enterprise Linux (EPEL)?

Solution Verified - Updated -


  • Red Hat Enterprise Linux (RHEL)


  • How to configure a Red Hat Enterprise Linux system to use Extra Packages for Enterprise Linux (EPEL)?


Important Notice

  • The following information has been provided by Red Hat, but is outside the scope of the posted Service Level Agreements and support procedures.
  • Installing unsupported packages does not necessarily make a system unsupportable by Red Hat Global Support Services
    • However, Red Hat Global Support Services will be unable to support or debug problems with packages not shipped in standard RHEL channels.
  • Installing packages from EPEL is done at the user's own risk.
  • The EPEL repository is a community supported repository hosted by the Fedora Community project.
  • The EPEL repository is not a part of Red Hat Enterprise Linux and does not fall under Red Hat's Production Support Scope of Coverage. The repository is considered an optional repository and is not tested by Red Hat quality engineers.

Enabling EPEL

  • Follow the directions on the EPEL website to install the epel-release package appropriate to the RHEL version of the system in question.
  • Ensure that you install the EPEL release that corresponds to the RHEL release you are running.
    • EPEL X must be installed on a RHEL X system (where X is 5/6/7/8 .. will probably continue in this fashion)

If the installation fails with No package epel-release available., you can install the package directly from http URL, as is also described on the EPEL website.

NOTE: Please do not confuse EPEL with the new Extras channel/repository in RHEL 7.


This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.


This article should be updated to use yum instead of rpm for the installation command.  Using rpm causes the next yum command to gripe thusly:

Warning: RPMDB altered outside of yum.

This site can’t be reached’s server DNS address could not be found. Search Google for fedoraproject org wiki EPEL ERR_NAME_NOT_RESOLVED

Loaded plugins: langpacks, product-id, search-disabled-repos, subscription- : manager rhel-7-desktop-extras-rpms | 3.8 kB 00:00
rhel-7-desktop-optional-rpms | 3.5 kB 00:00
rhel-7-desktop-rpms | 3.5 kB 00:00
(1/6): rhel-7-desktop-extras-rpms/x86_64/group | 104 B 00:01
(2/6): rhel-7-desktop-extras-rpms/x86_64/primary_db | 8.9 kB 00:00
(3/6): rhel-7-desktop-extras-rpms/x86_64/updateinfo | 4.5 kB 00:02
(4/6): rhel-7-desktop-optional-rpms/7Client/x86_64/group | 1.6 kB 00:01
(5/6): rhel-7-desktop-optional-rpms/7Client/x86_64/updatei | 2.2 MB 00:02
(6/6): rhel-7-desktop-optional-rpms/7Client/x86_64/primary | 9.0 MB 00:06
No package ntfs-3g available. Error: Nothing to do

unable to mount HPFS/NTFS/exFA on rhel 7

Until late 2018, Microsoft did not share it's IP with Linux. So at that time, things like ntfs-3g wouldn't be available in various 'indemnified' distributions (a real issue for users in countries like German, the UK, the US, et al.).

However, ntfs-3g is now build in EPEL since the change in IP stance. Here is the Fedora Project Koji page, including the EPEL builds for RHEL (.elX) ... -

Couldn't figure out how to enable extra packages so I can install nedit. The article just gives links to other pages that don't explain exactly how to enable extras for RH 6.

See the Wiki page link in the document,, just above the "How can I use these extra packages?" is the quick start which includes the yum install syntax for 6, 7, and 8 that will install the 'epel-release' package reference in the first line of "How can I use these extra packages?" ; "EPEL has an 'epel-release' package that includes gpg keys for package signing and repository information. Installing this package for your Enterprise Linux version should allow you to use normal tools such as yum to install packages and their dependencies..."

The instructions for installing the appropriate 'epel-release' package is in the quick start section of the wiki.

These solutions only work if you have an internet connected system with access to a repor. Installs of xdrp and tigervnc-server fail because yum cannot reach metadata for epel. Corrective actions REALLY need to take the isolated network owner into consideration.

You can download and install the epel-release package.

$ wget; $ sudo yum install epel-release-latest-7.noarch.rpm

Dear Red Hat, please include the correct material to cover RHEL 8 for this solution.

Perhaps this...

sudo dnf install

Thanks much!