Enterprise linux extra packages

Red Hat Enterprise Linux / CentOS Linux Enable EPEL (Extra Packages for Enterprise Linux) Repository

H ow do I enable EPEL (Extra Packages for Enterprise Linux) repo and install the packages under a RHEL / CentOS Linux server system?

EPEL (Extra Packages for Enterprise Linux) is a volunteer-based community effort from the Fedora project to create a repository of high-quality add-on packages that complement the Fedora-based Red Hat Enterprise Linux (RHEL) and its compatible spinoffs, such as CentOS and Scientific Linux.

Tutorial details
Difficulty level	Easy
Root privileges	Yes
Requirements	None
Est. reading time	10m

EPEL provide lots of packages for CentOS / RHEL, It is not part of RedHat or CentOS but is designed to work with these major distributions. Please note that EPEL only provides free and open source software unencumbered by patents or any legal issues. In short you will not find mp3, dvd and music / media player under EPEL. However, you will find many programs related to networking, monitoring, sys admin, programming and so on.

Packages are supplied in RPM format and in most cases are ready to use. Beware that some packages may break something and you should not blindly install those packages.

How to install EPEL and additional repositories on CentOS and Red Hat Linux?

1. Open a shell prompt.
2. Or login to a host called server1 using ssh client.
3. Type the following wget command: wget https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
4. Install epel using the following command: rpm -ivh epel-release-latest-7.noarch.rpm

Examples: How Do I Enable EPEL Repo under CentOS or RHEL Servers?

You need to type the following command as per your distro version / release.

Examples for RHEL 5.x / CentOS 5.x Users

Type the following command as root user to install repo:
# rpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-5.noarch.rpm

Examples for RHEL 6.x / CentOS 6.x Users

Type the following command as root user to install repo:
# rpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm

Examples for RHEL 7.x / CentOS 7.x Users

Type the following command as root user to install repo:
# rpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
OR use the following command:
# yum install epel-release.noarch
Sample outputs:

Fig.01: Installing repo on a CentOS 7 server

Protect Base Packages

You need to to protect base and core packages from EPEL and other repositories. Type the following command under RHEL 6/CentOS 6:

Note for RHN (Red Hat) users : You need to also enable the ‘optional’ repository to use EPEL packages as they depend on packages in that repository. This can be done by enabling the RHEL optional subchannel for RHN-Classic. For certificate-based subscriptions see RHEL Deployment Guide

# yum install yum-plugin-protectbase.noarch
Sample outputs:

RHEL 5/ CentOS 5 user type the following command to protect packages:
# yum install yum-protectbase.noarch
This plugin allows certain repositories to be protected. Packages in the protected repositories can’t be overridden by packages in non-protected repositories even if the non-protected repo has a later version.

How Do I Use EPEL Repo?

To list newly installed repo, enter:
# yum repolist
Sample output:

• No ads and tracking
• In-depth guides for developers and sysadmins at Opensourceflare✨
• Join my Patreon to support independent content creators and start reading latest guides:
  • How to set up Redis sentinel cluster on Ubuntu or Debian Linux
  • How To Set Up SSH Keys With YubiKey as two-factor authentication (U2F/FIDO2)
  • How to set up Mariadb Galera cluster on Ubuntu or Debian Linux
  • A podman tutorial for beginners – part I (run Linux containers without Docker and in daemonless mode)
  • How to protect Linux against rogue USB devices using USBGuard

Join Patreon ➔

Now, use the yum command to list, view and install the packages:
# yum search package-name
# yum install package-name
For example search htop package and install it:
# yum search htop
# yum install htop

See how to use yum command for installing and searching packages using various repos.

Further readings:

🐧 Get the latest tutorials on Linux, Open Source & DevOps via

Источник

The Extra Packages for Enterprise Linux (EPEL) repository

EPEL is a software package repository for CentOS and Red Hat Enterprise Linux (RHEL) which is maintained by IBMs subsidiary RedHat through their Fedora Team. It has a lot of «extra» packages the base repositories of those distributions do not have.

EPEL packages are currently available for CentOS, Scientific Linux and RHEL versions 6, 7 and 8 on Intel/AMD x64-64m PowerPC and ARM. The packages are based on packages from Fedora Linux but they are not for Fedora. Note that 32-bit x86 EPEL packages were discontinued with EPEL 7, packages for 32-bit x86 are available for version 6 which will soon be discontinued.

Enabling EPEL [ edit ]

CentOS and RHEL have a package called epel-release . Installing this package with

yum -y install epel-release

as root is enough to enable it.

This will create the two files /etc/yum.repos.d/epel.repo and /etc/yum.repos.d/epel-testing.repo where the first is for the stable EPEL packages and the latter is for the repositories experimental «testing» packages.

Useful packages that are not in the base repositories such as htop will become available once the epel-release package is installed.

Disabling EPEL can be done by either removing the epel-release package OR by simply changing the line enabled=1 to enabled=0 in /etc/yum.repos.d/epel.repo . Similarly, enabling the testing packages is done by changing enabled=0 to enabled=1 in /etc/yum.repos.d/epel-testing.repo

Tips [ edit ]

You can check what repositories are enabled by running yum repolist as root.

Источник

Extra Packages for Enterprise Linux (EPEL)

Welcome to the home of the EPEL Special Interest Group.

Quickstart

You may retrieve signed binary configuration files from one the above two links (varying by the major release number of the installation target machine). They may be automatically installed by root thus:

on RHEL 7 it is recommended to also enable the optional, extras, and HA repositories since EPEL packages may depend on packages from these repositories:

# subscription-manager repos —enable «rhel--optional-rpms» —enable «rhel--extras-rpms» —enable «rhel-ha-for-rhel-*-server-rpms»

CentOS Stream 8:

# dnf install epel-release

on RHEL 8 it is required to also enable the codeready-builder-for-rhel-8-*-rpms repository since EPEL packages may depend on packages from it:

# subscription-manager repos —enable «codeready-builder-for-rhel-8-$(arch)-rpms»

on CentOS 8 it is recommended to also enable the powertools repository since EPEL packages may depend on packages from it:

# dnf config-manager —set-enabled powertools

What is Extra Packages for Enterprise Linux (or EPEL)?

Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL).

EPEL packages are usually based on their Fedora counterparts and will never conflict with or replace packages in the base Enterprise Linux distributions. EPEL uses much of the same infrastructure as Fedora, including buildsystem, bugzilla instance, updates manager, mirror manager and more.

Learn more about EPEL in the following pages:

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:

What packages and versions are available in EPEL?

You can take a look on any of the available EPEL mirrors from our mirror list

Alternately, you can browse the package set:

EPEL 7: x86_64, ppc64le, sources (EPEL-7 for aarch64 is no longer supported as Red Hat ended support for this architecture).

END OF LIFE RELEASES

THESE ARE NO LONGER SUPPORTED

Due to major security changes in SSL in the last 10 years, older releases may not be able to directly point to these releases. As of 2021-01-22, EPEL-5 and 4 systems do not have the newer TLS1.2 algorithms that Internet servers are required to use for security reasons. The best method for working with these is to have a newer system mirror the entire 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 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. By default the stable EPEL 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‘ repository to use EPEL packages as they depend on packages in that repository. This can be done by enabling the RHEL optional subchannel for RHN-Classic. For certificate-based subscriptions see Red Hat Subscription Management Guide.

NOTE for RHEL 7 users with certificate subscriptions: EPEL 7 packages assume that the ‘optional‘ repository (rhel-7-server-optional-rpms for servers) and the ‘extras‘ repository (rhel-7-server-extras-rpms for servers) 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 packages assume that the ‘codeready-builder‘ repository is enabled. You can do this 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 install epel-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’s keys page: https://fedoraproject.org/keys

Can I rely on these packages?

The EPEL project strives to provide packages with both high quality and stability. However, EPEL is maintained by a community of people who generally volunteer their time and no commercial support is provided. It is the nature of such a project that packages will come and go from the EPEL repositories over the course of a single release. In addition, it is possible that occasionally an incompatible update will be released such that administrator action is required. By policy these are announced in advance in order to give administrators time to test and provide suggestions.

It is strongly recommended that if you make use of EPEL, and especially if you rely upon it, that you subscribe to the list. Traffic on this list is kept to a minimum needed to notify administrators of important updates.

History and background of the project

The EPEL project was born when Fedora maintainers realized that the same infrastructure that builds and maintains packages for Fedora would be great to also maintain add on packages for Enterprise Linux. Much of the early need was driven by what Fedora infrastructure needed on the RHEL machines that built and maintained Fedora. From there things have grown to a large collection of varied packages. See our history and Philosophy page for more information.

How can I contribute?

The EPEL SIG is always looking for interested folks to help out. We always need package maintainers, qa/testers, bug triagers, marketing and documentation writers. Please see our Joining EPEL page 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 IRC channel on Libera Chat offers real-time support for EPEL users and developers.

The is for general developer and SIG discussion.

The mailing list is a low volume mailing list for only important announcements.

The list is a list that gets information about package updates as they happen in the stable repository.

If you find a bug in a EPEL maintained package, please report it to https://bugzilla.redhat.com/ under the «Fedora EPEL» product.

Infrastructure issues (mirrors, repos, etc.) should be reported to Fedora releng.

The EPEL SIG meets on Wedensday every week in the channel at 21:00 UTC. Please check the time on the epel calendar; sometimes it can change or a meeting can be skipped. Feel free to join us! Logs of past meetings can be viewed in meetbot.

All Fedora Documentation content available under CC BY-SA 4.0 or, when specifically noted, under another accepted free and open content license.

Источник

Red Hat Customer Portal

Log in to Your Red Hat Account

Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

If you are a new customer, register now for access to product evaluations and purchasing capabilities.

Need access to an account?

If your company has an existing Red Hat account, your organization administrator can grant you access.

Red Hat Account

Customer Portal

For your security, if you’re on a public computer and have finished using your Red Hat services, please be sure to log out.

Select Your Language

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

Environment

Issue

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

Resolution

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.

References

• Product(s)
• Red Hat Enterprise Linux

• Component
• rpm
• yum

• Category
• Learn more

• Tags
• packages
• rhel
• rhel_5
• rhel_6
• rhel_7
• rhel_8

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.

8 Comments

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

fedoraproject.org’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) . — https://koji.fedoraproject.org/koji/packageinfo?packageID=2654

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, https://fedoraproject.org/wiki/EPEL, 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.

Источник