Bug 796410 - epel-release rpm install over http broke
Summary: epel-release rpm install over http broke
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: epel-release
Version: el5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michael Stahnke
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-22 20:20 UTC by John Sopko
Modified: 2013-11-13 13:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-13 13:54:45 UTC
Type: ---


Attachments (Terms of Use)

Description John Sopko 2012-02-22 20:20:41 UTC
Description of problem:

Installing the epel-release per the instructions does not work:

rpm -Uvh http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm


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


How reproducible:

Always


Steps to Reproduce:
1.

rpm -Uvh http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm

2.
3.
  
Actual results:

# rpm -Uvh http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm
Retrieving http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm
error: skipping http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm - transfer failed - Unknown or unexpected error
warning: u 0x96ae728 ctrl 0x96b00e0 nrefs != 0 (download.fedoraproject.org http)


Expected results:

epel-release rpm to install


Additional info:

This broke recently, tested on rhel5.7 and rhel5.8 that just came out and they both fail. If I use one of the mirrors it works:

# rpm -Uvh http://mirror.umd.edu/fedora/epel/5/i386/epel-release-5-4.noarch.rpm
Retrieving http://mirror.umd.edu/fedora/epel/5/i386/epel-release-5-4.noarch.rpm
warning: /var/tmp/rpm-xfer.DHABkI: Header V3 DSA signature: NOKEY, key ID 217521f6
Preparing...                ########################################### [100%]
   1:epel-release           ########################################### [100%]

Maybe something in the mirror redirecting causing the issue?

Is working on Red Hat 6.2

Comment 1 Todd Zullinger 2012-02-22 22:33:10 UTC
I'd guess that rpm from el5 doesn't support the redirection too.  If we updated the instructions to use http://dl.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm, we'd be alright (according to a quick test on a centos 5 box).  I'm not sure if that's desirable or not, so I didn't just update the wiki.

Comment 2 John Sopko 2012-02-23 12:44:51 UTC
We download the epel-release rpm as part of our automatic install process and this broke, was working fine. I will watch to see what URL is recommended. Thanks all.

Comment 3 Michael Stahnke 2012-11-05 05:57:13 UTC
I'm not sure what the best fix here is.  I can't fix RPM to follow redirects. Are people getting the link from the fedoraproject wiki?  We can update that.

Comment 4 John Sopko 2012-11-05 14:17:43 UTC
We have been using the http://dl.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm URL for rhel5, the rhel6 URL works. Was getting the links under:

http://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F

Comment 5 Jens Petersen 2013-11-13 04:26:39 UTC
(In reply to John Sopko from comment #4)
> http://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F

I don't quite understand: the links there are to repoview pages...

Comment 6 Jens Petersen 2013-11-13 04:27:54 UTC
So maybe can't fix?

Comment 7 Jens Petersen 2013-11-13 04:29:02 UTC
Or better to report the bug against RHEL5 rpm, specially if it is a regression.

Comment 8 John Sopko 2013-11-13 13:54:45 UTC
It has been sometime since I looked at. I beleive the links on the web page used to point to the URL instead of the repoview. The url we used used to have problems resolving a mirror but now works. I am closing.

http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm


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