[BlueOnyx:18897] Re: 5209R error messages for yum update

[Michael Stauber]

Hi Dirk,

> unfortunately  the result is the same:

That can happen when the mirrors aren't fully synchronized.

As you can see: The sqlite databases have a totally random name. If the
toplevel mirror updates, the sqlite database there gets a new name. YUM
is somewhat opportunistic. If it's provided with a list of mirrors, it
might use one during the beginning of the transaction and then in the
middle of the transaction it might decide: "The other one is faster, so
I use that one instead." But if that mirror hasn't fully synchronized
yet, then it might not find the sqlite database with the name it expects.

I just checked and the problem might have resolved itself in the
meantime. Despite that I did a manual sync of all mirrors just to be sure.

Please try it again and let us know if you still have issues.

-- 
With best regards

Michael Stauber