[Yum-devel] Making yum a bit more resistant to repository /
skvidal at phy.duke.edu
Sat May 7 18:53:02 EDT 2005
> 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
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.
> 3. If there is a simple (easily back-trackable) package that is
> blocking the update, tell the user which package it is and give them a
> very easy way to disable it (I think yum shell might be too
> complicated for many situations).
and what happens with -y?
> PS I read a post in some blog complaining that yum needs the network
> in order to perform yum erase, is there any reason for that? If not
> then let's get rid of it.
it needs the network to perform yum erase if it ends up needing to
More information about the Yum-devel