EPEL

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(What packages and versions are available in EPEL?)
m (info about optional repo for certificate-based subscriptions)
(16 intermediate revisions by 5 users not shown)
Line 13: Line 13:
 
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.
 
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 [[EPEL/FAQ | EPEL FAQ]] and [[About_EPEL | About EPEL]]
+
Learn more about EPEL in the following pages:
 +
 
 +
* [[EPEL/FAQ | EPEL FAQ]]
 +
 
 +
* [[About_EPEL |About EPEL]]
 +
 
 +
* [[EPEL/GuidelinesAndPolicies|EPEL Guidelines and Policies]]
  
 
== What packages and versions are available in EPEL? ==
 
== What packages and versions are available in EPEL? ==
Line 23: Line 29:
 
* EPEL 6: [http://dl.fedoraproject.org/pub/epel/6/i386/repoview/ i386], [http://dl.fedoraproject.org/pub/epel/6/x86_64/repoview/ x86_64], [http://dl.fedoraproject.org/pub/epel/6/ppc64/repoview/ ppc64], [http://dl.fedoraproject.org/pub/epel/6/SRPMS/repoview/ sources]
 
* EPEL 6: [http://dl.fedoraproject.org/pub/epel/6/i386/repoview/ i386], [http://dl.fedoraproject.org/pub/epel/6/x86_64/repoview/ x86_64], [http://dl.fedoraproject.org/pub/epel/6/ppc64/repoview/ ppc64], [http://dl.fedoraproject.org/pub/epel/6/SRPMS/repoview/ sources]
 
* EPEL 5: [http://dl.fedoraproject.org/pub/epel/5/i386/repoview/ i386], [http://dl.fedoraproject.org/pub/epel/5/x86_64/repoview/ x86_64], [http://dl.fedoraproject.org/pub/epel/5/ppc/repoview/ ppc], [http://dl.fedoraproject.org/pub/epel/5/SRPMS/repoview/ sources]
 
* EPEL 5: [http://dl.fedoraproject.org/pub/epel/5/i386/repoview/ i386], [http://dl.fedoraproject.org/pub/epel/5/x86_64/repoview/ x86_64], [http://dl.fedoraproject.org/pub/epel/5/ppc/repoview/ ppc], [http://dl.fedoraproject.org/pub/epel/5/SRPMS/repoview/ sources]
* EPEL 4: [http://dl.fedoraproject.org/pub/epel/4/i386/repoview/ i386], [http://dl.fedoraproject.org/pub/epel/4/x86_64/repoview/ x86_64], [http://dl.fedoraproject.org/pub/epel/4/ppc/repoview/ ppc], [http://dl.fedoraproject.org/pub/epel/4/SRPMS/repoview/ sources]
 
  
 
== How can I use these extra packages? ==
 
== How can I use these extra packages? ==
Line 29: Line 34:
 
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.  
 
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: You need to also enable the 'optional' repository to use EPEL packages as they depend on packages in that repository.
+
{{admon/tip|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 [https://access.redhat.com/kb/docs/DOC-11313 subchannel] for RHN-Classic. For certificate-based subscriptions see [https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/entitlements-and-yum.html#supplementary-repos RHEL Deployment Guide]}}
This can be done by enabling the RHEL optional [https://access.redhat.com/kb/docs/DOC-11313 subchannel] for example.
+
(Related profile is located at:/etc/yum.repos.d/epel-testing.repo)
+
 
+
If you are running an EL6 version:  [http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-5.noarch.rpm epel-release-6-5.noarch.rpm]
+
  
If you are running an EL5 version: [http://dl.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm epel-release-5-4.noarch.rpm]
+
If you are running an EL6 version, please visit here to get the newest 'epel-release' package for EL6: [http://download.fedoraproject.org/pub/epel/6/i386/repoview/epel-release.html The newest version of 'epel-release' for EL6]
  
If you are running an EL4 version: [http://dl.fedoraproject.org/pub/epel/4/i386/epel-release-4-10.noarch.rpm epel-release-4-10.noarch.rpm]
+
If you are running an EL5 version, please visit here to get the newest 'epel-release' package for EL5: [http://download.fedoraproject.org/pub/epel/5/i386/repoview/epel-release.html The newest version of 'epel-release' for EL5]
  
 
You can verify these packages and their keys from the Fedora project's keys page: https://fedoraproject.org/keys
 
You can verify these packages and their keys from the Fedora project's keys page: https://fedoraproject.org/keys
Line 53: Line 54:
 
There are many ways to communicate with the EPEL SIG and it's members:  
 
There are many ways to communicate with the EPEL SIG and it's members:  
  
* The #epel irc channel on irc.freenode.net offers real-time support for EPEL users and developers.  
+
* The {{fpchat|#epel}} IRC channel on irc.freenode.net offers real-time support for EPEL users and developers.  
  
 
* The [https://www.redhat.com/mailman/listinfo/epel-devel-list epel-devel-list] is for general developer and SIG discussion.  
 
* The [https://www.redhat.com/mailman/listinfo/epel-devel-list epel-devel-list] is for general developer and SIG discussion.  
Line 63: Line 64:
 
* If you find a bug in a EPEL maintained package, please report it to [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora+EPEL https://bugzilla.redhat.com/] under the "Fedora EPEL" component.
 
* If you find a bug in a EPEL maintained package, please report it to [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora+EPEL https://bugzilla.redhat.com/] under the "Fedora EPEL" component.
  
* The EPEL SIG meets every week in the #fedora-meeting irc channel at 20:30UTC. Feel free to join us! Logs of past meetings can be found at: http://meetbot.fedoraproject.org/teams/epel/
+
* The EPEL SIG meets every week in the {{fpchat|#fedora-meeting}} channel at 20:30 UTC. Feel free to join us! Logs of past meetings can be found at: http://meetbot.fedoraproject.org/teams/epel/
  
 
[[Category:EPEL]]
 
[[Category:EPEL]]
 
[[Category:Fedora sub-projects]]
 
[[Category:Fedora sub-projects]]

Revision as of 11:49, 19 October 2012

Banner468x120.png

Contents

Extra Packages for Enterprise Linux (EPEL)

Welcome to the home of the EPEL Special Interest Group.

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).

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 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 using repoview:

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.

Idea.png
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 RHEL Deployment Guide

If you are running an EL6 version, please visit here to get the newest 'epel-release' package for EL6: The newest version of 'epel-release' for EL6

If you are running an EL5 version, please visit here to get the newest 'epel-release' package for EL5: The newest version of 'epel-release' for EL5

You can verify these packages and their keys from the Fedora project's keys page: https://fedoraproject.org/keys

History and background of the project

The EPEL project was born when Fedora maintainers realized that the same infrastructure that builds and maintains packages 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 it's members:

  • The #epel[?] IRC channel on irc.freenode.net offers real-time support for EPEL users and developers.
  • The epel-announce mailing list is a low volume mailing list for only important announcements.
  • The epel-package-announce list is a list that gets information about package updates as they happen in the stable repository.