[Yum-devel] Making yum a bit more resistant to repository / network errors

[Ian Burrell]

On 5/7/05, seth vidal <skvidal at phy.duke.edu> wrote:
> 
> 
> > 1. When a repository can not be contacted when yum is started, disable
> > it for this run, displaying a warning.
> 
> This is extremely dangerous. an example:
> 
> far-repo contains foo-1.2-1
> 
> near-repo contains foo-1.2-1.mylocalcustomizations
> 
> installed: foo-1.1-1.mylocalcustomizations
> 
> you run yum update:
> 
> if near-repo is down for some misc reason then yum would update to
> foo-1.2-1 from 'far-repo'
> 
> If foo is important then the world might end for that user.
> 
> 
> > 2. If the primary metadata of a repository does not match the
> > checksum, disable the repo instead of bailing out.
> 
> Same problem as above.
> 

For both of these, it would be better to use the cached metadata for
the repositories instead of disabling the repository.  If the metadata
required is not available, like for the first access, then it should
be an error.  If the repository is not available, then it is would be
like the repository wasn't updated or yum is running from cache.

 - Ian