On Mon, 01 May 2000, you wrote:
> David Aspinall <[EMAIL PROTECTED]> writes:
>
> > Has anyone noticed an weird problem using the rpm command in quick
> > succession to upgrade packages? I occasionally get the spurious error
> > "cannot open database" between commands.
> >
> > This wasn't a problem until I started using autorpm to upgrade cooker
> > rpms automatically from a local mirror directory. It keeps crashing
> > part way through with "ERROR: RPM cannot open RPM database..."
> >
> > This happens with rpm-3.0.3-43mdk from M7 as well as current
> > rpm-3.0.4-0.12mdk
> >
> > rpm bug? anything else it could be?
>
> seems like the pb is update-menus which open the rpm database for reading.
>
> this is a pb. fred, any solution at hand?
Why the heck does it do that??? Isn't update-menus supposed to read from
/usr/lib/menus. What does it do in my rpm database??
Also is there any rpm util (or other) that scans my / -R and puts all files
into the rpm database?? As some packages is at time installed without an rpm
and would provide lib*.so.* wich a later package then requires?
Michael Irving
