Kevin Fenzi <ke...@scrye.com> writes: > On Sat, 13 Jul 2013 16:27:52 +0200 > lee <l...@yun.yagibdah.de> wrote: > >> Yes, this situation was the result of an upgrade that didn't finish. >> Are you saying that 'yum list installed' doesn't really tell you what >> is actually installed and you need to use 'rpm -V' instead? >> >> What are these placeholders? > > When rpm does an upgrade of a package it goes thru a number of steps. > It gets a transaction from yum, it checks it to make sure it would > run ok, then it runs it, during that it installs the new package(s) > runs any scriptlets, then once all new packages are installed, it > goes and removes the old packages from the database. > > Often when a transaction gets messed up in the middle, it doesn't get > to the very end part where it removes the no longer installed package > from the rpmdb. So, rpm then shows you have 'foo1' and 'foo2' both > installed, but foo1 really has already been replaced, just it's > database entry didn't get cleaned up. You can find this with 'rpm -V' > because 'rpm -V foo2' will show no problems and 'rpm -V foo1' will > show lots of changes (since foo1 is not really installed).
Oh I see -- thank you for the good explanation! >> prelink: /usr/bin/cjet: at least one of file's dependencies has >> changed since prelinking >> >> Pre-linking it again should fix that? > > Yes. Cool, then I don't have any problems with packages, as far as I can tell :) -- Fedora release 19 (Schrödinger’s Cat) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
