Hi,
Very THANKS!!!!!!!!! That worked great!!!!!
On Wed, 25 Oct 2000, Christopher Molnar wrote:
> I had the same rpm db problem that was reported here by a few others, and got
> a few emails on the subject as well. Here is how to fix (at least this worked
> for me).
>
> 1. Do not use Mandrake Update to update the RPM packages from 3.x to 4.x
> there are a ton of dependencies that you need to resolve first. popt and db3
> are some of the ones I know about. Mandrake Update will not install new
> packages, it just updates existing ones.
>
> 2. If you already found out #1 the hard way (like me), go to /var/lib/rpm as
> root and copy the *.rpm files to a safe location. Make sure that you have the
> db3*, and popt* packages installed and resolved all the dependency issues.
>
> 3. Delete the following files (or if you're chicken move them to another
> place):
> Basenames Packages
> Conflictname Providename
> Group Requirename
> Name Triggername
> (DO NOT DELETE THE ONES WITH THE .rpm extension).
>
> 4. now do an rpm -qa and you should get a message telling you that you need
> to do an rpm --rebuilddb as root. Now follow the instructions and type "rpm
> --rebuilddb".
>
> This solved the problem on one of my test machines. Note, you may also have
> to run "update-menus" following the database rebuild as your menus may be
> messed up as well.
>
> Hope this helps someone!
>
> -Chris
>
>
--
Saludos
--------------------------------------------------
Fernando Monera Daroqui
email: [EMAIL PROTECTED]
--------------------------------------------------
Tlf: (91) 542 28 00
Instituto de Investigaci�n Tecnol�gica
Escuela T�cnica Superior de Ingenier�a (ICAI)
Universidad Pontificia Comillas
C/ Sta Cruz de Marcenado no. 26
28015 MADRID - SPAIN
--------------------------------------------------
No se ha usado ning�n producto comercial para
escribir �ste mensaje.
linux reg N�: 94004 (http://counter.li.org)
--------------------------------------------------
