Topic: changes to yum

[fixit]

Looks like some changes has been made at CentOS,

http://mirror.centos.org/centos-4/4.1/readme

This directory (and version of CentOS) is depreciated.  For normal users,
you should use /4/ and not /4.1/ in your path. Please see this FAQ
concerning the CentOS release scheme:

http://www.centos.org/modules/smartfaq/faq.php?faqid=34

If you know what you are doing, and absolutely want to remain at the 4.1
level, go to http://vault.centos.org/ for packages.

Instructions to change yum repositories for CentOS 4.1

Note: just change the yum.conf in the /etc first or you will have to do this twice, an update of yum gets installed with the updates, which will change all settings back to default

If you wanting to go back to 4. Change the entries http://mirror.centos.org/centos/4.1 to http://mirror.centos.org/centos/4

cd /home/e-smith/db

Backup yum_repositories

edit yum_repositories

 remove all entries to http://mirror.centos.org/centos/4.1

and change them to http://vault.centos.org/4.1

# updated: Sat Oct 22 22:10:17 2005
addons=repository|BaseURL|http://vault.centos.org/4.1/addons/$basearch|EnableGroups|no|GPGCheck|yes|Name|CentOS - addons|status|disabled
base=repository|BaseURL|http://vault.centos.org/4.1/os/$basearch|EnableGroups|no|GPGCheck|yes|Name|CentOS - os|status|enabled
centosplus=repository|BaseURL|http://vault.centos.org/4.1/centosplus/$basearch|EnableGroups|no|GPGCheck|yes|Name|CentOS - centosplus|status|disabled
contrib=repository|BaseURL|http://vault.centos.org/4.1/contrib/$basearch|EnableGroups|no|GPGCheck|yes|Name|CentOS - contrib|status|enabled
extras=repository|BaseURL|http://vault.centos.org/4.1/extras/$basearch|EnableGroups|no|GPGCheck|yes|Name|CentOS - extras|status|disabled
smeaddons=repository|BaseURL|http://mirror.contribs.org/smeserver/releases/7/addons/$basearch|EnableGroups|yes|GPGCheck|yes|Name|SME Server - addons|status|enabled
smedev=repository|BaseURL|http://mirror.contribs.org/smeserver/releases/7/dev/$basearch|EnableGroups|yes|GPGCheck|yes|Name|SME Server - dev|status|disabled
smeos=repository|BaseURL|http://mirror.contribs.org/smeserver/releases/7/os/$basearch|EnableGroups|yes|GPGCheck|no|Name|SME Server - os|status|enabled
smetest=repository|BaseURL|http://mirror.contribs.org/smeserver/releases/7/test/$basearch|EnableGroups|yes|GPGCheck|yes|Name|SME Server - test|status|disabled
smeupdates=repository|BaseURL|http://mirror.contribs.org/smeserver/releases/7/updates/$basearch|EnableGroups|yes|GPGCheck|yes|Name|SME Server - updates|status|enabled
smeupdates-testing=repository|BaseURL|http://mirror.contribs.org/smeserver/releases/7/updates-testing/$basearch|EnableGroups|yes|GPGCheck|yes|Name|SME Server - updates testing|status|disabled
testing=repository|BaseURL|http://vault.centos.org/4.1/testing/$basearch|EnableGroups|no|GPGCheck|yes|Name|CentOS - testing|status|disabled
updates=repository|BaseURL|http://vault.centos.org/4.1/updates/$basearch|EnableGroups|no|GPGCheck|yes|Name|CentOS - updates|status|enabled

cd /etc/e-smith/db/yum_repositories/force

edit the BaseURL within the following directories

/etc/e-smith/db/yum_repositories/force/addons

/etc/e-smith/db/yum_repositories/force/centosplus

/etc/e-smith/db/yum_repositories/force/base

/etc/e-smith/db/yum_repositories/force/contrib

/etc/e-smith/db/yum_repositories/force/extras

/etc/e-smith/db/yum_repositories/force/testing

/etc/e-smith/db/yum_repositories/force/updates

To make changes permanent

/sbin/e-smith/expand-template /etc/yum.conf
/sbin/e-smith/yum_update_dbs
/etc/e-smith/events/actions/initialize-default-databases

cd /etc

check yum.conf to see if changes have been made

try yum update

when updates are complete run

signal-event post-upgrade
signal-event reboot

[gordonr]

Looks like some changes has been made at CentOS,

I see that you have raised this in the bug tracker (many thanks), but please only raise 7.0beta issues in the bug tracker.

This allows us to solve the problem once, rather than dealing with the problem, various possible fixes, and the fallout from each of those.

Please don't post fixes for 7.0beta here - please suggest them in the bug tracker, and only there.

For the record, you don't need to edit the databases in any case - changing the force files and running initialize-default-databases will do it. And I wouldn't solve the problem this way, except as a temporary measure, and that shouldn't be required for 7.0beta, since it is a test release.