-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Timothy Murphy wrote: > Tim wrote: > >> I've seen plenty of times where you'll do an update that worked, then >> moments later try to do another (on the same PC or another), and you've >> unfortunately picked the moment that the repo has been changed. You're >> stuck with repeatedly doing a "yum clean metadata", "yum update", for a >> while until the repos get their act together. > > I'm surprised there is not some simple way > of informing the user that the repo is being updated. > One would imagine the repodata could contain a message to that effect > (with an estimate of how long it would take) > which yum could read and repeat. > Sure, that could be done! With the net effect of you trying to update again, which of course you should be smart enough to figure out without being told. Scott -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFEruqU5mBKdb7VQEcRAqfuAKCpPvpnpZSwt37PXAC4L6ohdwdx4wCgj5dN 1cNqcGJsZ7syRAv/Ovxrvi8= =JTky -----END PGP SIGNATURE-----
