On Tue, Aug 21, 2001 at 01:14:10PM -0700, tluxt wrote:
> Thanks Ben for your prompt reply! :)
>
> --- Ben Collins <[EMAIL PROTECTED]> wrote:
> > Actually, to do a fresh install of woody, you download the woody
> > boot-floppies, and install woody. That's pretty simple, right? :)
> >
> > I don't
Thanks Ben for your prompt reply! :)
--- Ben Collins <[EMAIL PROTECTED]> wrote:
> Actually, to do a fresh install of woody, you download the woody
> boot-floppies, and install woody. That's pretty simple, right? :)
>
> I don't suggest upgrading to woody yet. Wait a day or two for the new
> glibc
On Tue, Aug 21, 2001 at 01:40:48AM -0700, tluxt wrote:
> Err,
>
> I think I would rather have titled that message:
> "How to accomplish a fresh install of today's Woody system."
> rather than "How to upgrade ...",
> because I the procedure I gave there (and want)
> is about doing a fresh install
And it works for me as well.
Thanks Johnny!
wrote:
>perl: error while loading shared libraries: libdb.so.3: cannot open shared
>objec
>t file: No such file or directory
>
>I've done a Google search and seen this come up a lot but can't find a fix.
>
>Is my system now broken beyond repair or is there a way
the trick i did was:
i check /lib/ for any libdb* and then just symlinked the one with the highest
version to /lib/libdb.so.3 (maybe do ln -s /lib/libdb.so.2 /lib/libdb.so.3
), i ran ldconfig, and it worked...
hope this will help...
(--[ on Tuesday 21 August 2001 11:40, P Kirk bothered us
Good call! It is a broken symlink.
enterprise:/home/patrick# ls -al /lib/libdb.so.3
lrwxrwxrwx1 root root 14 Aug 21 10:00 /lib/libdb.so.3 ->
libdb.so.3.old
enterprise:/home/patrick# locate libdb.so.3.old
enterprise:/home/patrick#
So, what do I need to do to get a libdb.s
dpkg -x /' if it
still
| wouldnt want to install.
What missing files?
enterprise:/home/patrick# locate libdb.so.3
/lib/libdb.so.3
Its there but not being used. Should it be linked somewhere else?
|
| oh yeah, dont forget to run ldconfig when you've created new links to
| libraries.
|
--:/
oh yeah, dont forget to run ldconfig when you've created new links to
libraries.
greetz
(--[ on Tuesday 21 August 2001 11:10, P Kirk bothered us with ]::
^ perl: error while loading shared libraries: libdb.so.3: cannot open shared
^ objec
^ t file: No such file or directory
^
^ I've d
perl: error while loading shared libraries: libdb.so.3: cannot open shared
objec
t file: No such file or directory
I've done a Google search and seen this come up a lot but can't find a fix.
Is my system now broken beyond repair or is there a way to fix this?
Manually compile gli
Err,
I think I would rather have titled that message:
"How to accomplish a fresh install of today's Woody system."
rather than "How to upgrade ...",
because I the procedure I gave there (and want)
is about doing a fresh install.
Of course, the answer is relevant to doing an upgrade of
an existi
de stable -> testing today, avoiding the libdb.so.3 bug?
("today", so we are able to do this upgrade without
having to wait for updates to propagate from unstable to testing.)
Several list readers have been very helpful with replies on this topic
already.
(See:
libdb.so.3 woo
try manually installing libdb2.
--- Badiane Ka <[EMAIL PROTECTED]> wrote:
> I am getting this error message when I try to run many
> commands. the error message is libdb.so.3: cannot
> open shared object file.
>
> I was upgrading a potato install to woody and I keep
>
I am getting this error message when I try to run many
commands. the error message is libdb.so.3: cannot
open shared object file.
I was upgrading a potato install to woody and I keep
getting this error. I cannot complete the
installation.
I would appreciate any help you guys can provide
>
> > The other is a compatibility problem with
> > libdb.so.3 which is (was) a symlink to libdb2.so.something, and evidently
> > shouldn't've been.
>
> > Both these have been fixed recently, and are currently
> > being built for all arches.
>
&
all'ing libc6 and db2 before anything
> else (especially perl).
> The other is a compatibility problem with
> libdb.so.3 which is (was) a symlink to libdb2.so.something, and evidently
> shouldn't've been.
> Both these have been fixed recently, and are currently
>
lems: one is an upgrade ordering problem,
which is fixed by apt-get install'ing libc6 and db2 before anything
else (especially perl). The other is a compatibility problem with
libdb.so.3 which is (was) a symlink to libdb2.so.something, and evidently
shouldn't've been. Both these hav
debian.org/debian-user/2001/debian-user-200108/msg00019.html
error message with "libdb.so.3"
http://lists.debian.org/debian-user/2001/debian-user-200108/msg00269.html
From:
http://lists.debian.org/debian-user/2001/debian-user-200108/thrd5.html
libdb.so.3
http://lists.debian.org/debian-u
PROTECTED] wrote:
>> >perl: error while loading shared libraries: libdb.so.3: cannot open shared
>> >object file: No such file or directory
>[...]
>> >I looked of libdb.so.3 is in the /lib directory and there it was.
>>
>> You need libdb3. the libdb.so.3 i
On Thu, Aug 16, 2001 at 07:02:32PM -0600, John Galt wrote:
> On Thu, 16 Aug 2001 [EMAIL PROTECTED] wrote:
> >perl: error while loading shared libraries: libdb.so.3: cannot open shared
> >object file: No such file or directory
[...]
> >I looked of libdb.so.3 is in the /lib d
You need libdb3. the libdb.so.3 is actually a symlink, part of the libdb2
package. When you get libdb3, it'll be replaced with the actual
libdb.so.3
On Thu, 16 Aug 2001 [EMAIL PROTECTED] wrote:
>First I tried to install nmap_2.54.28.BETA-1_i386.deb
>
>It said needs >=libc6_2.
<[EMAIL PROTECTED]> writes:
> First I tried to install nmap_2.54.28.BETA-1_i386.deb
>
> It said needs >=libc6_2.2.3-1
>
> So I got libc6_2.2.3-9_i386.deb and installed it.
This was probably a bad idea. I would suggest reinstalling the
version of libc6 you were previously using and building you
ace nmap 2.54.28.BETA-1 (using nmap_2.54.28.BETA-
1_i386.deb) ...
Unpacking replacement nmap ...
Setting up nmap (2.54.28.BETA-1) ...
perl: error while loading shared libraries: libdb.so.3: cannot open shared
object file: No such file or directory
dpkg: error processing nmap (--install):
subprocess p
On Sunday 12 August 2001 11:43, Michael P. Soulier wrote:
> Hey people.
>
> So, I was told that the solution to upgrading to unstable from stable
> and getting the missing libdb.so.3 library was to upgrade to testing first.
> That did not work. The same thing happened.
>
On Sun, Aug 12, 2001 at 01:45:59PM +1000, CaT wrote:
>
> Dunno if this was suggested but have you tried putting in the src lines
> for unstable in the apt sources.list file and then doing
>
> apt-get -b source libdb3 (or whatever the package is called)
>
> in some work dir?
Nope. I worked a
On Sat, Aug 11, 2001 at 11:43:20PM -0400, Michael P. Soulier wrote:
> Hey people.
>
> So, I was told that the solution to upgrading to unstable from stable and
> getting the missing libdb.so.3 library was to upgrade to testing first. That
> did not work. The same
Hey people.
So, I was told that the solution to upgrading to unstable from stable and
getting the missing libdb.so.3 library was to upgrade to testing first. That
did not work. The same thing happened.
I'm working around it again by ftping the lib from my working box, but
On Sat, Aug 04, 2001 at 02:35:58PM -0400, Joe Bouchard wrote:
> On Sat, Aug 04, 2001 at 12:31:35AM -0400, Michael P. Soulier wrote:
> > On Sat, Aug 04, 2001 at 08:46:32AM +0800, Lindsay Allen wrote:
> > >
> > > I had this problem too. I copied libdb.so
On Sat, Aug 04, 2001 at 12:31:35AM -0400, Michael P. Soulier wrote:
> On Sat, Aug 04, 2001 at 08:46:32AM +0800, Lindsay Allen wrote:
> >
> > I had this problem too. I copied libdb.so.3 from another box to /lib.
> >
> > Later while doing an apt upgrade I got a me
On Sat, Aug 04, 2001 at 08:46:32AM +0800, Lindsay Allen wrote:
>
> I had this problem too. I copied libdb.so.3 from another box to /lib.
>
> Later while doing an apt upgrade I got a message saying something like
> "libdb.so.3 is not a symlink."
>
> But it all w
> man: error while loading shared libraries: libdb.so.3:
> cannot open shared object file: No such file or
> directory
>
> /usr/bin/perl: error while loading shared libraries:
> libdb.so.3: cannot open shared object file: No such
> file or directory
I had this problem to
Oops! I replied but I've got the same message again.
Maybe some problem. Anyway I will try to answer again
and address some more questions below. Thanks!
--- Ben Collins <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 02, 2001 at 11:55:56AM -0700, Changkil
> Lee wrote:
> > Hi!
> >
> > I tried to i
> > Hi!
> >
> > I tried to install my printer "epson stylus color
> 860"
> > and I found that my system didn't have a
> "printtool"
> > package. I installed an unstable "printtool"
> package
> > which caused me to install lots of extras as
> follows.
> > Later I found that there is a testing ve
On Thu, Aug 02, 2001 at 11:55:56AM -0700, Changkil Lee wrote:
> Hi!
>
> I tried to install my printer "epson stylus color 860"
> and I found that my system didn't have a "printtool"
> package. I installed an unstable "printtool" package
> which caused me to install lots of extras as follows.
> L
2 locales lpr-ppd pconf-detect
After that I cannot run apt-get or dpkg properly. It
complains about libdb.so.3. To make it worse I get
the following error messages when I try to use man
command and xemacs and many others. Can I remove the
unstable packages and restore m
Oops,
Sorry, I meant:
http://lists.debian.org/debian-user-0009/msg04260.html
Krafty
Michael Smith wrote:
> I ftp'ed libdb.so.3 from a working box, stuck it in the right place on the
> machine, and
> then did an upgrade. It's ugly, but effective, since there's an u
uot;Pascal
Hos"
user):
http://lists.debian.org/debian-user-0009/msg04260.html
Enjoy,
Krafty
Thomas Halahan wrote:
> Andrew,
>
> I have had very similar problems. I upgraded to libc6
> libc6_2.1.94-1, which caused certain programs (apache, gnome-apt) to
> not locale libdb.
I ftp'ed libdb.so.3 from a working box, stuck it in the right place on the
machine, and
then did an upgrade. It's ugly, but effective, since there's an upgrade that
overwrites the "borrowed" version completely.
Thomas Halahan wrote:
> Andrew,
>
> I have had
nome-apt) to
> > not locale libdb.so.3. So I upgraded my libdb2 and this didn't help.
> > As encouraged I upgraded to libc6_2.1.94-3 but I could not becuase
> > it required libdb.so.3 which was missing. So I downdraded libc6 and
> > my ldconfig dissapeard. I'm now
On Wed, Oct 04, 2000 at 02:18:17PM +, Thomas Halahan wrote:
> Andrew,
>
> I have had very similar problems. I upgraded to libc6
> libc6_2.1.94-1, which caused certain programs (apache, gnome-apt) to
> not locale libdb.so.3. So I upgraded my libdb2 and this didn't help
Andrew,
I have had very similar problems. I upgraded to libc6
libc6_2.1.94-1, which caused certain programs (apache, gnome-apt) to
not locale libdb.so.3. So I upgraded my libdb2 and this didn't help.
As encouraged I upgraded to libc6_2.1.94-3 but I could not becuase
it required libdb
On Sun, Oct 01, 2000 at 07:33:15PM -0500, [EMAIL PROTECTED] wrote:
> The last time that everything functioned normally was before I
> did "dist-upgrade". Anything involving "libdb.so.3" doesn't work.
> Perl won't work, Exim won't work, and Apa
The last time that everything functioned normally was before I
did "dist-upgrade". Anything involving "libdb.so.3" doesn't work.
Perl won't work, Exim won't work, and Apache won't work. I upgraded
to the newest version of libdb2 while I still cou
[EMAIL PROTECTED] wrote:
> If I type "locate libdb.so.3" it says that "/gnu/lib/libdb.so.3" and
> "/usr/lib/libdb.so.3" exist, but when I check myself, they actually
> don't.
Don't know about exim, but if locate thinks it's there, it pr
When I try to load exim, it says:
exim: error while loading share libraries: libdb.so.3: cannot open
shared object file: No such file or directory
If I type "locate libdb.so.3" it says that "/gnu/lib/libdb.so.3" and
"/usr/lib/libdb.so.3" exist, but when I che
tanked with the same error message that you got. What I did was
> ftp to
> another machine, grab /usr/lib/libdb.so.3, and move it to the right place on
> the
> broken box. Then I immediately did an upgrade and the problem fixed itself
> with the
> upgrade (the package in question g
Ihad the same problem a couple of days ago--the hard party was that the library
was
missing, so I couldn't upgrade to a working version. It tried to preconfigure,
and
then perl tanked with the same error message that you got. What I did was ftp
to
another machine, grab /usr/lib/libdb
On Sat, 30 Sep 2000, P.J.Walsh wrote:
> dpkg is choking on some upgrades, showing libdb.so.3 missing... dpkg
> -S doesn't help. To what does it belong?
To find out which package it belongs to go to www.debian.org and go to the
packages page. You can look up which package it belongs to.
On 30-Sep-2000 Ben Collins wrote:
>
> This is no longer true. Follow the threads. libc6 2.1.94-3 has zero
> issues.
Thanks, I will upgrade now.
--
Andrew
On Sat, Sep 30, 2000 at 09:54:56PM +, Pollywog wrote:
>
> On 30-Sep-2000 P.J.Walsh wrote:
> > dpkg is choking on some upgrades, showing libdb.so.3 missing... dpkg
> > -S doesn't help. To what does it belong?
>
> It belongs to the libdb package but the prob
On 30-Sep-2000 P.J.Walsh wrote:
> dpkg is choking on some upgrades, showing libdb.so.3 missing... dpkg
> -S doesn't help. To what does it belong?
It belongs to the libdb package but the problem is with libc6.
I had to revert to the previous versions of libc6, libc6-dev, and locale
dpkg is choking on some upgrades, showing libdb.so.3 missing... dpkg
-S doesn't help. To what does it belong?
--
Patrick Walsh
Edmonton AB CA
52 matches
Mail list logo
