0003476: yum refuses to upgrade anything if filelist.xml.gz is damaged in the repository or if the server does not respond

CentOS Bug Tracker

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0003476

CentOS-5

yum

public

2009-04-02 11:14

2013-01-21 16:07

Reporter

icebearsoft

Priority

normal

Severity

major

Reproducibility

always

Status

closed

Resolution

no change required

Platform

OS Version

Product Version

5.2

Target Version

Fixed in Version

Summary

0003476: yum refuses to upgrade anything if filelist.xml.gz is damaged in the repository or if the server does not respond

Description

When yum starts upgrade or update, it looks into repositories. If its filelist.xml.gz is damaged or the server does not respond and no alternative repository is known. yum refuses to update/upgrade anything although most files are accessible and do not depend on the defunct repository. It would be better if yum just did not upgrade files from the wrong repository and files depending on the contents of the wrong repository and upgraded everything else.

Additional Information

This is my persistent error message from running "yum upgrade" or "yum update":

filelists.xml.gz 100% |=========================| 137 kB 00:00
http://linuxdownload.adobe.com/linux/i386/repodata/filelists.xml.gz: [^] [Errno -1] Metadata file does not match checksum
Trying other mirror.
Error: failure: repodata/filelists.xml.gz from adobe-linux-i386: [Errno 256] No more mirrors to try.

Tags

No tags attached.

Attached Files

Relationships

Notes
(0009024) Charlie Brady (reporter) 2009-04-02 20:03	If yum cannot read filelists.xml.gz from a repository, it does now know which packages that repository contains. If it were to proceed, it might "upgrade files from the wrong repository" which is just what you say that you don't want it to do. You have an easy workaround - --disable-repo=adobe-linux-i386 (or permanently disable the repo which no longer works).

(0016310) c_patr02 (reporter) 2013-01-21 07:35	I had the same problem on a 5.8 version, but a yum clean all has solved the problem and the update workd like expected

Issue History
Date Modified	Username	Field	Change
2009-04-02 11:14	icebearsoft	New Issue
2009-04-02 20:03	Charlie Brady	Note Added: 0009024
2013-01-21 07:35	c_patr02	Note Added: 0016310
2013-01-21 16:07	toracat	Status	new => closed
2013-01-21 16:07	toracat	Resolution	open => no change required