up2date problems

[Jim Cornette]

Rick Stevens wrote:
> Carlos Qualls wrote:
> 
>> running up2date I get the following error:
>>
>> # up2date-nox -u
>>
>> Fetching package list for channel: fedora-core-1...
>>
>> Fetching
>> http://fedora.redhat.com/releases/fedora-core-1/headers/header.info...
>> ########################################
>>
>> Fetching package list for channel: updates-released...
>>
>> Fetching
>> http://fedora.redhat.com/updates/released/fedora-core-1/headers/header.info... 
>>
>> ########################################
>>
>> Fetching Obsoletes list for channel: fedora-core-1...
>>
>> Fetching Obsoletes list for channel:
>> updates-released...
>>
>> Fetching rpm headers...
>> error: rpmts_HdrFromFdno: MD5 digest: BAD
>> Expected(ef91247cc6fbabdfd4eee934c37ab91a) !=
>> (489b1a7613a023c6992cdfd3512c5835)
>> There was a fatal RPM error. The message was:
>> Error reading header
> 
> 
> Have you tried "yum update" instead of up2date?
> 

Having Yum, apt and up2date all installed and configured help out with 
many updating problems.

I upgraded a bit with apt, then yum and got so far. Now I am using 
up2date to get further along on bringing up this Lorma system to a 
developmental installation level.

My advice, configure them all with your choice of repositories. Use one 
to try to install the rpm. If it fails, try another.

apt-get is the most dangerous updating program though. It pulled my 
system out from under me on several ocassions.

I think the problem above is with a congested server. A configuration 
with a mirror would probably resolve the problem or at least reduce it 
significantly.

Jim