Re: Re: SUG: Automatic RPM database verification and repair

["Jeff Johnson" <n3npq jbj gmail com>]

On 11/28/06, Tony Nelson <tonynelson georgeanelson com> wrote:
> 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.

RPM creates the dbpath lazily if it does not exist. Whether that is a feature
or a bug depends on who you are talking to.

The current behavior (creating the path lazily) makes creating chroots
easier, one does not have to do the explicit
   mkdir -p /path/to/chroot/var/lib/rpm

OTOH, invocations of rpm with random dbpaths can/will litter the end-point
with lazily created empty directories.

73 de Jeff

> --
> ____________________________________________________________________
> TonyN.:'    The Great Writ     <mailto:tonynelson georgeanelson com>
>       '      is no more.             <http://www.georgeanelson.com/>
>
> _______________________________________________
> Rpm-list mailing list
> Rpm-list redhat com
> https://www.redhat.com/mailman/listinfo/rpm-list