t
On Mon, 3 Aug 2009, Martin Vogt wrote:
Seth Vidal wrote:
Here's what I suspect is happening:
- yum is running the rpm transaction
- the transaction finishes.
- yum goes to check that everything it was supposed to do is done.
- it finds that a package it was installing is not installed b/c the
rpmdb error you're getting means rpm was not able to register the entry
in the rpmdb
So your first order of business is: fix the db error you're getting.
After that I suspect the other problems will go away.
I dont get the rpm db error with the single kernel-soure rpm.
(I suspect the db error only appers with this "strange" rpm
and "enough" (lets say > 1024) update rpms too)
Currently I update only the single rpm, I'm currently
bisecting the kernel-source.spec file. :)
But the funny thing is that the update works without errors
when it comes from the local filesystem, if it comes from http
the error is back.
Martin
what do you mean "comes from http"? all pkgs are downloaded before yum
runs against them and the pkgs are verified vs their checksums and gpg
signatures. So an operation from a local disk and an operation from a repo
on an http server should be the same.
-sv
_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxx
http://lists.baseurl.org/mailman/listinfo/yum
