Guillaume Cottenceau wrote:
>Salane <[EMAIL PROTECTED]> writes:
>
>>rpm -q kernel
>>kernel-2.4.13-9mdk
>>kernel-2.4.13-12mdk
>>kernel-2.4.13-12mdk
>>kernel-2.4.13-12mdk
>>kernel-2.4.13-12mdk
>>kernel-2.4.13-9mdk
>>kernel-2.4.13-10mdk
>>kernel-2.4.13-11mdk
>>kernel-2.4.13-12mdk
>>kernel-2.4.13-9mdk
>>kernel-2.4.13-8mdk
>>kernel-2.4.13-9mdk
>>kernel-2.4.13-12mdk
>>kernel-2.4.13-12mdk
>>kernel-2.4.13-12mdk
>>kernel-2.4.13-12mdk
>>kernel-2.4.13-12mdk
>>kernel-2.4.13-9mdk
>>kernel-2.4.13-9mdk
>>kernel-2.4.13-12mdk
>>kernel-2.4.13-12mdk
>>kernel-2.4.13-12mdk
>>kernel-2.4.13-12mdk
>>
>>and when I try to uninstall
>>
>>rpm -e kernel-2.4.13-9mdk
>>error: "kernel-2.4.13-9mdk" specifies multiple packages
>>
>
>--allmatches
>
>
Well excuse me, but I think that 'rpm --rebuilddb' SHOULD fix this kind
of mess. I am utterly amazed at how absolutely impotent this supposed
database sanity tool actually is. In my experience it is next to
useless for any but the most trivial rpm database corruptions. And
thats my two cents on the matter.
