Re: [SLE] Problem with Perl Berkeley DB?
Thanks again for the advice Zentara. I build and installed BerkeleyDB ( the latest version ) from sources and copied over the db.h file to the Suse installed db.h location. I then built and tested the Berkely DB perl interface. It complained about having incompatible versions of db. So I also overwrote some library files to fix that little issue. That seemed to allow the Berkeley DB perl test to run better. However, Postfix was unable to handle its .db files now. So I backed everything out so that I could keep postfix running. Now the question is, do I need to compile Postfix after upgrading Berkeley DB or something? Thanks, Jim
On Fri, 20 Jun 2003 10:41:49 -0700 (PDT) jrn@oregonhanggliding.com (Jim Norton) wrote:
Thanks for the information. I actually did grab the sleepycat Berkeley DB tar ball but was afraid to install it. I wasn't sure if I'd end up breaking my installation of Cyrus.
I've actually never uninstalled an RPM. How do I do this? Do I need access to the CD with the RPM?
I'll tell you that yast will scream and moan if you try to remove db, it will keep bugging you about unresolved dependencies. It might be easier just to remove the rpm without yast. With yast, you go to install/remove software.
You need to get the name of the rpm's. They are on cd 1 and 2, on 8.1 mine is /CD1/suse/i586/db-4.0.14-182.i586.rpm /CD2/suse/i586/db-devel-4.0.14-182.i586.rpm
So you do : rpm -e db-4.0.14-182.i586.rpm rpm -e db-devel-4.0.14-182.i586.rpm
Then they are gone, but yast still thinks they are there. There is another method, of installing new packages from source, and letting yast do it, I think it is called "checkinstall". It will put the updated info in the yast database. You might want to ask the list, if you want to do it that way.
Like I said earlier, when I did it, I didn't even bother to uninstall the db and db-devel rpms. Everything went in and worked fine. Except occaisionally, when compiling source programs which needed the db header files, it would complain about db.h being wrong. It depends on how the program's makefile searches the include files, usually they search properly, but sometimes they find the old file first. I just copied the new db.h over the old one, and everything worked. That probably the easiest way.
Remember, if you find that you "break some existing software", you can always just reinstall the old rpms.
Good luck, you will be alright.
-- use Perl; #powerful programmable prestidigitation
On Sun, 22 Jun 2003 23:01:16 -0700 (PDT) jrn@oregonhanggliding.com (Jim Norton) wrote:
I build and installed BerkeleyDB ( the latest version ) from sources and copied over the db.h file to the Suse installed db.h location.
I then built and tested the Berkely DB perl interface. It complained about having incompatible versions of db.
So I also overwrote some library files to fix that little issue.
That seemed to allow the Berkeley DB perl test to run better. However, Postfix was unable to handle its .db files now.
So I backed everything out so that I could keep postfix running. Now the question is, do I need to compile Postfix after upgrading Berkeley DB or something?
It sure sounds like it. Welcome to the tangled web of upgrading software with multiple-interdependencies. -- use Perl; #powerful programmable prestidigitation
participants (2)
-
jrn@oregonhanggliding.com
-
zentara