RE: SUG: Automatic RPM database verification and repair

["Stanley, Jon" <Jon Stanley savvis net>]

>
>Rpm does something odd when it is given a non-existent or 
>non-full path to
>a RPM database: it creates a new RPM database there.  If it is 
>given a full
>path (or a proper relative path) to a broken RPM database it 
>will report
>the errors.  For proper operation, the script requires a full path to a
>real RPM database.  Arguably this is a deficiency in rpm's "--verifydb"
>option.
>-- 

Correct - if given a database path that does not exist, I would expect
rpm to generate an error on --verifydb.  I would submit it as a bug if
it creates a new database in that path instead.