What to do when rpm verification fails

[Jim Cornette]

Andras Simon wrote:
> On 7/7/06, Robin Laing <Robin.Laing at drdc-rddc.gc.ca> wrote:
> 
>>
>> Another option is to try is
>>    rpm -F --replacepkgs {package name}
>> This will re-install the rpm, even if it exists.  This should fix the
>> issue of file permissions and possibly changed/corrupted files.
> 
> Some of these "installs" involved downgrading (because the install dvd
> is out of date for many packages), that's why I used --force (it
> implies --oldpackage). Anyway, this part went quite smoothly, except
> for stuff like
> 
> missing     /usr/share/system-config-securitylevel/checklist.pyc
> missing     /usr/share/system-config-securitylevel/firstboot_selinux.pyc
> missing     /usr/share/system-config-securitylevel/scs_checklist.pyc
> missing     /usr/share/system-config-securitylevel/securitylevel.pyc
> missing     /usr/share/system-config-securitylevel/selinuxPage.pyc
> missing     
> /usr/share/system-config-securitylevel/system-config-securitylevel.p
> yc
> missing     /usr/share/system-config-securitylevel/trustedchecklist.pyc
> 
> showing up in rpm -Va, which I suspect is a packaging bug and has
> nothing to do with my recent troubles. But I may be wrong about
> this...
> 
> Andras

I get a lot of missing files on occasion with system-config-* programs 
when I verify the rpms.

Most of the time, I just remove the database entry then use yum to 
install the package again. Other times, I just remove the package using 
rpm and r\then reinstall the package with yum.

Why system-config-* packages end up with missin files is unknown to me 
though.

Jim

-- 
When a person goes on a diet, the first thing he loses is his temper.