Jeff asked me to post this for him. Here’s what he has to say, timestamp retrodated to his email to me:

Instead of using up2date when first installing a Fedora Core 2 box, and watching up2date seemingly hang indefinately while resolving dependencies in GNOME or KDE, I decided to just use yum directly. However, as FC2 comes out of the box (so to speak), yum does not work properly at the command line.

The error message I was getting when running “yum update” as root was:

> Gathering header information file(s) from server(s)
> Server: Fedora Core 2 - i386 - Base
> Error - /var/cache/yum/base/header.info cannot be found
> Please ask your sysadmin to update the headers on this system.

The solution, as I found on one of the Duke mailing lists, was actually for Fedora Core 1 but the same method applied. As root, type “rm -rf /var/cache/yum/base” and then run “yum update” again. This should allow yum to run normally. I hope this helps!

-Jeff

Jeff asked me to post this for him. Here’s what he has to say, timestamp retrodated to his email to me:

Instead of using up2date when first installing a Fedora Core 2 box, and watching up2date seemingly hang indefinately while resolving dependencies in GNOME or KDE, I decided to just use yum directly. However, as FC2 comes out of the box (so to speak), yum does not work properly at the command line.

The error message I was getting when running “yum update” as root was:

> Gathering header information file(s) from server(s)
> Server: Fedora Core 2 - i386 - Base
> Error - /var/cache/yum/base/header.info cannot be found
> Please ask your sysadmin to update the headers on this system.

The solution, as I found on one of the Duke mailing lists, was actually for Fedora Core 1 but the same method applied. As root, type “rm -rf /var/cache/yum/base” and then run “yum update” again. This should allow yum to run normally. I hope this helps!

-Jeff