I read the readme in unstable after installing KDE 2.1 by slamming it in
there. but I understood Chris Molnar to be upgrading from the latest
developmental version of Mandrake 7.2. I was just trying to upgrade a
vanilla 7.2 installation and it worked, kind of.
There is a package called db1? that's an awfully short name for an rpm
file. they usually go on for at least a sentence. I guess it's db1
something or other. I'll check usr/lib and the cooker files to see.
-----Original Message-----
From: Van Holland <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Monday, February 12, 2001 8:03 PM
Subject: Re: [Cooker] Upadating to glibc-2.2
>There is a seperate package db1 that has that file now. It keeps it in
>/usr/lib. I'd check to see if you have that package installed.
>
>Also let me recommend the README in unstable....Mandrake directory on
>kde.org. It shows you the proper order on loading the KDE 2.1 packages
>without having to force anything.
>
>Good luck!
>
>--
>Van Holland; MCSE+I; Master CNE
>Public Key: 0xDDB2572D
>[EMAIL PROTECTED]
>
>
>
>>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
>
>On 2/12/01, 7:48:36 PM, pablito <[EMAIL PROTECTED]> wrote regarding Re:
>[Cooker] Upadating to glibc-2.2:
>
>> I tried these instructions on 7.2. They worked.
>
>> then, I tried upgrading KDE 2.0 to 2.1 beta by using
>> rpm -Uhv --force --nodeps. I left out jdk-sun. The last step of that
>> upgrade is rpm --rebuilddb && update-menus -v && init 6.
>
>> during the upgrade, some of the packages were complaining that they
>couldnt
>> find libdb.so.2 and the last command said it couldn't find that file
>either,
>> and so didn't rebuild or update anything.
>
>> KDE booted up anyway and pretty much worked, except for kpackage and the
>> drak configuration utilities. They also couldn't find libdb.so.2 and
>didn't
>> work.
>
>> there must be a simple explanation. lib.so.conf points to the
>> i386-glibc21-linux/lib directory, and there is a libdb.so.2 file in
>there.
>
>
