OurDelta

RHEL repository problems

Bug #373548 reported by Cafuego
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OurDelta
New
Undecided
evil_steve

Bug Description

The yum repository setup as described on http://ourdelta.org/centos does not work.

I'm setting up on an x86_64 RHEL5 server machine:

$ lsb_release -a
LSB Version: :core-3.1-amd64:core-3.1-ia32:core-3.1-noarch:graphics-3.1-amd64:graphics-3.1-ia32:graphics-3.1-noarch
Distributor ID: RedHatEnterpriseServer
Description: Red Hat Enterprise Linux Server release 5.3 (Tikanga)
Release: 5.3
Codename: Tikanga

Trying to install, it seems that $release version is '5Server' on this machine, whilst the repo expects it to be '5'.

$sudo yum install Mysql-OurDelta-server
Loaded plugins: rhnplugin
http://mirror.ourdelta.org/yum/CentOS/5Server/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://northernmost.uk.mirror.ourdelta.org/yum/CentOS/5Server/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://nerdvana.us.mirror.ourdelta.org/yum/CentOS/5Server/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://cc.us.mirror.ourdelta.org/yum/CentOS/5Server/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: ourdelta. Please verify its path and try again

I can use a local mirrorlist and change '\$releaseversion' to '5', but then it defaults to installing i386 packages, not x86_64 ones.

Cafuego (cafuego)
Changed in ourdelta:
assignee: nobody → evil_steve (steve-nerdvana)
Revision history for this message
evil_steve (steve-nerdvana) wrote :

That would be correct.

This boils down to the way RHEL does their channel subscription resolution in yum, and the best way to solve it is to break the RHEL and Centos configs apart to reference different paths in the repo file (the paths can essentially be a symbolic link on the mirrors).

Revision history for this message
evil_steve (steve-nerdvana) wrote :

Further information provided by OP showed this server was managed from a central RH Satellite server. To resolve this, the channel would need to be added to Satellite and the server subscribed to to that channel. The satellite server would then resolve $releasever correctly and it should work from there.

I hope to have a spacewalk server setup to confirm this behaviour.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.