You are not logged in.
Pages: 1
$ man bc
man: error while loading shared libraries: libdb-4.6.so: cannot open shared object file: No such file or directory$ man tar
man: error while loading shared libraries: libdb-4.6.so: cannot open shared object file: No such file or directory$ man man
man: error while loading shared libraries: libdb-4.6.so: cannot open shared object file: No such file or directory
$ ls /usr/lib | grep libdb
libdb-4.5.so
libdb-4.7.a
libdb-4.7.so
libdb-4.so
libdb.a
libdb.so
libdb_cxx-4.5.so
libdb_cxx-4.7.a
libdb_cxx-4.7.so
libdb_cxx-4.so
libdb_cxx.a
libdb_cxx.so
libdbh-1.0.so.1
libdbh-1.0.so.1.0.0
libdbh.a
libdbh.so
libdbus-1.a
libdbus-1.so
libdbus-1.so.3
libdbus-1.so.3.4.0
libdbus-glib-1.so
libdbus-glib-1.so.2
libdbus-glib-1.so.2.1.0
Any idea how I may be able to fix this?
edit: I am using 'testing' repository. Seems db 4.7 is in testing. So this must be a man package issue that needs be updated. For now can i just symlink to db-4.7.so without much trouble?
Last edited by rooloo (2008-07-09 15:55:01)
Offline
you *could* do that but i recommend attempting a pacman -Syu instead to see if you can update it before you make a hack like that that may be likely to bite you in the ass later -- also it is likely you will have to link the other files that have version numbers in that list but are lacking a v4.6 -- hopefully pacman will sort this out for you -- hope this helps
Last edited by bbs (2008-07-09 15:57:45)
(quaqmire talking about a dude getting his tubes tied)
sex kinda looses its appeal without the potency -- its like a cobra without the venom -- i mean what do you have then....? -- a belt?
Offline
You seem to be using different repos in your install. When I do a $ls /usr/lib | grep libdb, all I get is libdb-4.6...etc. You've got 4.5's and 4.7's. All I have enabled is core, extra and community. I believe 4.7 is in testing. I read somewhere here that if you want testing and not have it mess things up so much, you should place it after the community repo in your /etc/pacman.conf file.
Edit: Darn, took too long to post.
Last edited by bgc1954 (2008-07-09 16:06:40)
Time is a great teacher, but unfortunately it kills all its pupils ... - Louis Hector Berlioz
Offline
@rooloo
libdb-4.6.so is owned by db. Downgrade the db package: http://wiki.archlinux.org/index.php/Downgrade_packages.
Testing does not mean the same thing in Arch that it does in, say, Debian. It is more like Debian unstable. You must be willing to have your system break if you run testing, and you must be willing to file bug reports. Get your feet wet with Arch first, then enable testing.
For now can i just symlink to db-4.7.so without much trouble?
No. There will be differences in the 2 versions which might break your system.
Also, welcome to Arch!
Offline
Make sure your entire system is up to date with a pacman -Syu. I am not seeing that error with man and the testing repo.
And as tigermesh said, never symlink files to solve these problems... it can only lead to bigger, more obscure problems.
Offline
Looks like you're using man-db instead of the normal man. man-db uses DB to store the manpage cache, so it links to DB. AUR/Community/your own packages haven't been recompiled for the DB update.
Offline
Looks like you're using man-db instead of the normal man. man-db uses DB to store the manpage cache, so it links to DB. AUR/Community/your own packages haven't been recompiled for the DB update.
boom! ty, I will now update my packages. why I am using this man-db? I have no idea!
EDIT: now I see COLOR as well. yay! Still need find out why I was using man-db instead.
Last edited by rooloo (2008-07-10 12:40:04)
Offline
Pages: 1