Hello, random Googler. This one is for you.
Today's post is about some issues I've been having at work with an old Web server running Fedora Core 2. For various reasons, I have been attempting to update the packages on this old piece of junk to the latest available versions. (That is, the latest available for FC2; I'm not going to try the Herculean task of updating to 7.) For those of you who are not interested in technical details on server administration, this post is not for you; it is for the random Googler who found this page by searching for some of the keywords in the below explanation. Keywords like 4f2a6fd2, 6cdf2cc1, yum, GPG, and zlib.
The reason that I am posting this is that I have spent several days figuring this shit out for myself, with only minimal aid provided by Google searches; there seems to be no information anywhere detailing this set of problems, and I'd like to make life a little easier for the next poor bastard caught in this situation.
Problem #1 is finding a yum repository. The Fedora Legacy Project has shut down. There are still a goodly number of mirrors operational as of this writing, but my copy of yum rejected a number of them based on errors like the following:
Gathering header information file(s) from server(s) Server: Fedora Core 2 - via Fedora Legacy Project retrygrab() failed for: http://[...]/fedora/2/os/i386/headers/header.info Executing failover method failover: out of servers to try Error getting file http://[...]/fedora/2/os/i386/headers/header.info [Errno 4] IOError: HTTP Error 404: Not Found
A couple of URLs I've found that do have the header.info file are:
and the latter, conveniently, is even the top option in the default /etc/yum.conf . So just comment out the Main Fedora Updates section and uncomment the pertinent lines under Fedora Legacy Project.
Aside gripe: b2evo apparently automatically turns URLs into links, even if they are obviously bullshit URLs. Update 2008-01-17: Switching to WordPress took care of this problem.)
Then comes my next problem:
warning: rpmts_HdrFromFdno: V3 DSA signature: NOKEY, key ID 4f2a6fd2 Error: Could not find the GPG Key necessary to validate pkg /var/cache/yum/updates-released/packages/pango-1.4.1-1.i386.rpm Error: You may want to run yum clean or remove the file: /var/cache/yum/updates-released/packages/pango-1.4.1-1.i386.rpm Error: You may also check that you have the correct GPG keys installed
It turns out that key is actually located on the default install. Just do:
rpm --import /usr/share/doc/fedora-release-2/RPM-GPG-KEY-fedora
You'll probably also want to import http://www.fedoralegacy.org/FEDORA-LEGACY-GPG-KEY.
You'd think that would be the end of my GPG problems. But you'd be wrong.
warning: rpmts_HdrFromFdno: V3 DSA signature: NOKEY, key ID 6cdf2cc1 Error: Could not find the GPG Key necessary to validate pkg /var/cache/yum/crash-hat/packages/zlib-188.8.131.52-0.i386.rpm Error: You may want to run yum clean or remove the file: /var/cache/yum/crash-hat/packages/zlib-184.108.40.206-0.i386.rpm Error: You may also check that you have the correct GPG keys installed
Now this one turned out to be a bit tricky. All my Google searches for "6cdf2cc1" turned up people trying to install a certain open-source anti-virus program (I'm omitting its name because if you're like me, you'll see page after page of results mentioning that program and then attempt a Google search which removes that search term). Very few mentioned zlib, and none told me where I could find the appropriate GPG key.
After some further banging my head against the wall, it occurred to me to ask myself what set zlib apart from all the other packages, since they hadn't given me any errors.
As it turns out, zlib was the only package hanging out in the /var/cache/yum/crash-hat/packages directory. It was, in fact, from a different repository, not the Fedora Legacy repos listed above.
So I Googled crash-hat and the very first match was titled CrashHat YUM Repository. It linked the appropriate GPG-KEY and that was all I needed; at last I could update my server. Now it is merely ancient, not decrepit.
With any luck, this may help fix some of the other issues the server's been having. Perhaps more on those at a later date.