[users] links to RPMs on usage page

Ian Young ian at iay.org.uk
Thu Nov 22 10:13:00 CET 2012


There isn't an issue tracker on https://github.com/repoforge/repoforge.github.com, so…

I noticed that the usage page at http://repoforge.org/use/ has a lot of links to RPMs and the statement that:

> Use rpm -ivh package-filename to install the rpmforge-release package (also works with URLs)

At least with the rpm in CentOS 5, that last part isn't correct, at least for the URLs given:

> # rpm -ivh http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.i386.rpm
> Retrieving http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.i386.rpm
> error: skipping http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.i386.rpm - transfer failed - Unknown or unexpected error

The link is valid to download the RPM, but not to install it directly.  This seems to be because there's a long chain of redirects involved:

> # wget http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.i386.rpm
> --2012-11-22 09:00:35--  http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.i386.rpm
> Resolving pkgs.repoforge.org... 78.46.17.228
> Connecting to pkgs.repoforge.org|78.46.17.228|:80... connected.
> HTTP request sent, awaiting response... 302 Found
> Location: http://rpmforge.sw.be/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.5.2-2.el5.rf.i386.rpm [following]
> --2012-11-22 09:00:35--  http://rpmforge.sw.be/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.5.2-2.el5.rf.i386.rpm
> Resolving rpmforge.sw.be... 78.46.17.228
> Connecting to rpmforge.sw.be|78.46.17.228|:80... connected.
> HTTP request sent, awaiting response... 301 Moved Permanently
> Location: http://tree.repoforge.org/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.5.2-2.el5.rf.i386.rpm [following]
> --2012-11-22 09:00:35--  http://tree.repoforge.org/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.5.2-2.el5.rf.i386.rpm
> Resolving tree.repoforge.org... 78.46.17.228
> Connecting to tree.repoforge.org|78.46.17.228|:80... connected.
> HTTP request sent, awaiting response... 301 Moved Permanently
> Location: http://apt.sw.be/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.5.2-2.el5.rf.i386.rpm [following]
> --2012-11-22 09:00:35--  http://apt.sw.be/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.5.2-2.el5.rf.i386.rpm
> Resolving apt.sw.be... 193.1.193.67
> Connecting to apt.sw.be|193.1.193.67|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 12680 (12K) [application/x-redhat-package-manager]
> Saving to: `rpmforge-release-0.5.2-2.el5.rf.i386.rpm'

The most useful fix for this would probably be to change the links to point at the final resolved location for the packages, as if you take the last location in the chain rpm does work:

> # rpm -ivh http://apt.sw.be/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.5.2-2.el5.rf.i386.rpm
> Retrieving http://apt.sw.be/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.5.2-2.el5.rf.i386.rpm
> Preparing...                ########################################### [100%]
>    1:rpmforge-release       ########################################### [100%]


Alternatively, I suppose, the page could stop making the claim that the URLs work directly with rpm.  I think that's less helpful, though.

	-- Ian



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4813 bytes
Desc: not available
URL: <http://lists.repoforge.org/pipermail/users/attachments/20121122/ee9dbe23/attachment-0002.p7s>


More information about the users mailing list