As of Sep 20, 2004, Fedora Core 1 has been transferred to the Fedora Legacy Project.
See the Official Announcement from Fedora Project.
To use yum repository from Fedora Legacy Project, update your /etc/yum.conf as following:
FN Site Search
FN Blog Login
[main]
cachedir=/var/cache/yum
debuglevel=2
logfile=/var/log/yum.log
pkgpolicy=newest
distroverpkg=fedora-release
tolerant=1
exactarch=1
retries=20
[base]
name=Fedora Core $releasever - $basearch - Base
baseurl=http://download.fedoralegacy.org/fedora/$releasever/os/$basearch/
[updates-released]
name=Fedora Core $releasever - $basearch - Released Updates
baseurl=http://download.fedoralegacy.org/fedora/$releasever/updates/$basearch/
Here is the actual run of "yum update" using fedoralegacy.org repository:
[root@www root]# yum update Gathering header information file(s) from server(s) Server: Fedora Core 1 - i386 - Base Server: Fedora Core 1 - i386 - Released Updates Finding updated packages Downloading needed headers Resolving dependencies Dependencies resolved I will do the following: [update: cups 1:1.1.19-13.2.legacy.i386] [update: cups-libs 1:1.1.19-13.2.legacy.i386] [update: httpd-manual 2.0.51-1.4.legacy.i386] [update: httpd-devel 2.0.51-1.4.legacy.i386] [update: httpd 2.0.51-1.4.legacy.i386] [update: cups-devel 1:1.1.19-13.2.legacy.i386] [update: mod_ssl 1:2.0.51-1.4.legacy.i386] Is this ok [y/N]: y Getting cups-1.1.19-13.2.legacy.i386.rpm cups-1.1.19-13.2.legacy.i 100% |=========================| 2.5 MB 00:02 Getting cups-libs-1.1.19-13.2.legacy.i386.rpm cups-libs-1.1.19-13.2.leg 100% |=========================| 98 kB 00:00 Getting httpd-manual-2.0.51-1.4.legacy.i386.rpm httpd-manual-2.0.51-1.4.l 100% |=========================| 1.4 MB 00:01 Getting httpd-devel-2.0.51-1.4.legacy.i386.rpm httpd-devel-2.0.51-1.4.le 100% |=========================| 143 kB 00:00 Getting httpd-2.0.51-1.4.legacy.i386.rpm httpd-2.0.51-1.4.legacy.i 100% |=========================| 1.0 MB 00:00 Getting cups-devel-1.1.19-13.2.legacy.i386.rpm cups-devel-1.1.19-13.2.le 100% |=========================| 132 kB 00:00 Getting mod_ssl-2.0.51-1.4.legacy.i386.rpm mod_ssl-2.0.51-1.4.legacy 100% |=========================| 84 kB 00:00 Running test transaction: Test transaction complete, Success! httpd 100 % done 1/14 cups-libs 100 % done 2/14 cups 100 % done 3/14 httpd-manual 100 % done 4/14 httpd-devel 100 % done 5/14 cups-devel 100 % done 6/14 mod_ssl 100 % done 7/14 Completing update for cups - 8/14 Completing update for cups-libs - 9/14 Completing update for httpd-manual - 10/14 Completing update for httpd-devel - 11/14 Completing update for httpd - 12/14 Completing update for cups-devel - 13/14 Completing update for mod_ssl - 14/14 Updated: cups 1:1.1.19-13.2.legacy.i386 cups-libs 1:1.1.19-13.2.legacy.i386 httpd-manual 2.0.51-1.4.legacy.i386 httpd-devel 2.0.51-1.4.legacy.i386 httpd 2.0.51-1.4.legacy.i386 cups-devel 1:1.1.19-13.2.legacy.i386 mod_ssl 1:2.0.51-1.4.legacy.i386 Transaction(s) Complete [root@www root]#
The goal of The Fedora Legacy Project is to work with the Linux community to provide security and critical bug fix errata packages for select End of Life Red Hat Linux and Fedora Core distributions. This will allow for a longer effective life for those releases.
The Fedora Legacy Update Advisories are located at http://fedoralegacy.org/updates/
# wget http://download.fedoralegacy.org/redhat/7.3/legacy-utils/i386/yum-1.0.3-6.0.7.x.legacy.noarch.rpm
As usual, I couldn't wait to try it out so I just installed it with following command:
# rpm -Uvh yum-1.0.3-6.0.7.x.legacy.noarch.rpm
Then I noticed, its own yum.conf was saved as yum.conf.rpmnew which means unless you update your own yum.conf based on yum.conf.rpmnew, your yum client is still pointing to old yum repository instead of new fedoralegacy yum repository.
I wanted to be "clean" install. I didn't want any "old" configuration files so I've decided to start over.
# rpm -e yum --> This is how you remove current yum package # rm -rf /etc/yum.conf --> I just wanted to make sure # rm -rf /etc/yum.conf.rpmsave --> This is what created when you remove yum package # rm -rf /etc/yum.conf.rpmnew --> This is what created when you install new yum package if old yum package exist # rpm -Uvh yum-1.0.3-6.0.7.x.legacy.noarch.rpm --> Now "clean" install with new yum configuration file
Check the "new" yum configuration file with following command:
# cat /etc/yum.conf [main] cachedir=/var/cache/yum debuglevel=2 logfile=/var/log/yum.log pkgpolicy=newest exactarch=1 exclude=kernel* tolerant=1 [base] name=Red Hat Linux $releasever base baseurl=http://download.fedoralegacy.org/redhat/$releasever/os/$basearch gpgcheck=1 [updates] name=Red Hat Linux $releasever updates baseurl=http://download.fedoralegacy.org/redhat/$releasever/updates/$basearch gpgcheck=1 #[updates-testing] #name=Red Hat Linux $releasever updates-testing #baseurl=http://download.fedoralegacy.org/redhat/$releasever/updates-testing/$basearch #gpgcheck=1 [legacy-utils] name=Fedora Legacy utilities for Red Hat Linux $releasever baseurl=http://download.fedoralegacy.org/redhat/$releasever/legacy-utils/$basearch gpgcheck=1
NOTE: I've set tolerant to 1 (yes) to be more tolerant to error message I was getting during the first yum check-update run.
For more information, type "man yum.conf"
To import GPG Keys for your yum client, type following command:
# gpg --import /usr/share/doc/yum-1.0.3/*GPG-KEYYes, the new yum pacakge you just installed comes with 3 GPG-KEY:
# ls -1 /usr/share/doc/yum-1.0.3/*GPG-KEY /usr/share/doc/yum-1.0.3/Fedora-GPG-KEY /usr/share/doc/yum-1.0.3/Fedora-Legacy-GPG-KEY /usr/share/doc/yum-1.0.3/RPM-GPG-KEY
# rpm -qa | grep legacy cvs-1.11.1p1-9.7.legacy yum-1.0.3-6.0.7.x.legacy screen-3.9.11-4.legacy slocate-2.7-1.7.3.legacy tcpdump-3.6.3-17.7.3.4.legacy
If you have "Legacy" Red Hat Linux as described above running in your environment, I highly recommend The Fedora Legacy Project as we are dependent on our own server and proudly support as an important part of our project.