Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 870686 - URL points to
Summary: URL points to
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: epel-release
Version: el6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Michael Stahnke
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2012-10-27 22:43 UTC by Anssi Johansson
Modified: 2012-12-19 18:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-12-19 18:29:33 UTC
Type: Bug

Attachments (Terms of Use)

Description Anssi Johansson 2012-10-27 22:43:07 UTC
Description of problem:

The URL contained in epel-release-6-7.noarch.rpm points to a deprecated URL

This also shows up on as a link to

Version-Release number of selected component (if applicable):


Steps to Reproduce:

1. yum info epel-release 
Actual results:

"URL :"

Expected results:

"URL :"

Comment 1 Anssi Johansson 2012-10-28 17:33:33 UTC
epel-release in EL5 uses , that would be fine as well.

Comment 2 Fedora Update System 2012-11-05 05:08:01 UTC
epel-release-6-8 has been submitted as an update for Fedora EPEL 6.

Comment 3 Fedora Update System 2012-11-05 17:02:06 UTC
Package epel-release-6-8:
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing epel-release-6-8'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2012-12-19 18:29:36 UTC
epel-release-6-8 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.