Re: yum critical: <XYZ> was supposed to be installed but is not
Seth Vidal <[email protected]>
| Newsgroups | gmane.linux.rpm.yum |
|---|---|
| Message-ID | <[email protected]> |
On Mon, 3 Aug 2009, Martin Vogt wrote: > Martin Vogt wrote: >> Hello list, >> >> I have tracked down a critical yum error message: >> >> >>> kernel-source-2.6.27.25-0.1.1.x86_64 >>> was supposed to be installed but is not! >> > > Now it gets interesting. > > I get this error on "yum update": > >> Running Transaction >> Updating : kernel-source-2.6.27.25-0.1.1.x86_64 > >> Cleanup : kernel-source-2.6.27.23-0.1.1.x86_64 > >> kernel-source-2.6.27.25-0.1.1.x86_64 was supposed to be installed but >> is not! > > But _not_ on: > > yum update > /var/cache/yum/R0_os11.1/packages/kernel-source-2.6.27.25-0.1.1.x86_64.rpm > > (which is the same rpm of course) > >> Updating: >> kernel-source >> x86_64 2.6.27.25-0.1.1 /kernel-source-2.6.27.25-0.1.1.x86_64 > [......] >> Running Transaction >> Updating : kernel-source-2.6.27.25-0.1.1.x86_64 > >> Cleanup : kernel-source-2.6.27.23-0.1.1.x86_64 > >Transaction time: 41.489 > > so running yum update does not work but > yum update /path/to/rpm.rpm works(!) > > I use yum 3.2.23 > including the lates patches from rawhide: > > Patch0: installonlyn-enable.patch > Patch1: yum-mirror-priority.patch > Patch2: yum-manpage-files.patch > Patch3: yum-multilib-policy-best.patch > Patch4: yum-HEAD.patch > Patch5: no-more-exactarchlist.patch > Patch6: yum_no_deprected.patch > > (The previous version 3.2.23 without the pachtes had the same problem btw.) > 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. -sv