I wanted to install the rpmforge-release package on a new install and get the following. Do others have the same problem?
b51:~ rpm -ivvvvvvvh http://packages.sw.be/rpmforge-release/rpmforge- release-0.3.6-1.el5.rf.i386.rpm Retrieving http://packages.sw.be/rpmforge-release/rpmforge-release-0.3.6- 1.el5.rf.i386.rpm D: ... as /var/tmp/rpm-xfer.qQEt9n D: failed to open http://packages.sw.be/rpmforge-release/rpmforge-release -0.3.6-1.el5.rf.i386.rpm: error: skipping http://packages.sw.be/rpmforge-release/rpmforge-release- 0.3.6-1.el5.rf.i386.rpm - transfer failed - Unknown or unexpected error D: May free Score board((nil))
wgetting this file and installing is fine.
I then tried another one: b51:~ rpm -ivh http://download.fedora.redhat.com/pub/epel/5/i386/epel- release-5-3.noarch.rpm Retrieving http://download.fedora.redhat.com/pub/epel/5/i386/epel-release -5-3.noarch.rpm warning: /var/tmp/rpm-xfer.9GjegW: Header V3 DSA signature: NOKEY, key ID 217521f6 Preparing... ########################################### [100%] 1:epel-release ########################################### [100%]
so, downloading via rpm is ok.
Kai
Kai Schaetzl wrote:
I wanted to install the rpmforge-release package on a new install and get the following. Do others have the same problem?
b51:~ rpm -ivvvvvvvh http://packages.sw.be/rpmforge-release/rpmforge- release-0.3.6-1.el5.rf.i386.rpm Retrieving http://packages.sw.be/rpmforge-release/rpmforge-release-0.3.6- 1.el5.rf.i386.rpm D: ... as /var/tmp/rpm-xfer.qQEt9n D: failed to open http://packages.sw.be/rpmforge-release/rpmforge-release -0.3.6-1.el5.rf.i386.rpm: error: skipping http://packages.sw.be/rpmforge-release/rpmforge-release- 0.3.6-1.el5.rf.i386.rpm - transfer failed - Unknown or unexpected error D: May free Score board((nil))
wgetting this file and installing is fine.
I then tried another one: b51:~ rpm -ivh http://download.fedora.redhat.com/pub/epel/5/i386/epel- release-5-3.noarch.rpm Retrieving http://download.fedora.redhat.com/pub/epel/5/i386/epel-release -5-3.noarch.rpm warning: /var/tmp/rpm-xfer.9GjegW: Header V3 DSA signature: NOKEY, key ID 217521f6 Preparing... ########################################### [100%] 1:epel-release ########################################### [100%]
so, downloading via rpm is ok.
go look at the http code in rpm :D
- KB
Karanbir Singh wrote on Thu, 03 Jul 2008 18:22:21 +0100:
go look at the http code in rpm :D
do you get the same result?
Kai
On Thu, Jul 3, 2008 at 2:31 PM, Kai Schaetzl maillists@conactive.com wrote:
go look at the http code in rpm :D
do you get the same result?
This is a known issue with rpm's http code. It doesn't do cookies. It can't really follow redirects (302 or otherwise) well, and generally it's a hack. That's why Karanbir said to look at rpm's http handling code. It was written back when dinosaurs roamed the internet, and was pounded into rpm with a rather large mallet.
Jim Perrin wrote on Thu, 3 Jul 2008 15:47:03 -0400:
This is a known issue with rpm's http code. It doesn't do cookies. It can't really follow redirects (302 or otherwise) well, and generally it's a hack.
Ah, well, now I understand. Yes, there occurs a redirect. It once used to work, with apt.sw.be, which obviously wasn't a redirect. Thanks, it's the first time I've seen this, I think. Or at least so long ago that I forgot about the last one.
Kai