On Wed, 20 Oct 2010 19:41:15 -0430, Patrick wrote: > On Wed, 2010-10-20 at 23:02 +0200, Walter Cazzola wrote: > > today I got a machine fail (a blackout) during a yum update and after Have you tried running "yum-complete-transaction" yet? > > that all my attempt to update my machine end with the following error: > [...] > > What you're seeing is a yum error (actually a repo out of synch in all > likelihood), not a yum crash. Announcing that yum crashes is a serious > issue. A repo inconsistency is liable to go away on its own. Where does this "repo out of synch" theory come from? When an x86_64 multiarch repo is updated, its metadata contains matching (!) pairs of x86_64 and i686 packages [1]. That is, same version and release, because the packages are built from the same src.rpm, and the multiarch repo compose tool fetches the packages from the same build. A repo that is "out of sync" either doesn't offer the latest metadata at all or doesn't carry all packages yet - 404 Not Found errors. But Yum would not proceed with installing updates if packages referred to in the metadata are not found. The only case when a multiarch package like postgresql-libs would differ in version-release between x86_64 and i686 would be if the repo compose tool contained a bug (or the packages were changed in a way they would not be selected for multiarch anymore). -- [1] https://admin.fedoraproject.org/updates/postgresql-8.4.5-1.fc13 -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
