From: Richard Hirst <rhirst@linuxcare.com>
To: Tom <tom@Alaskatech.org>
Cc: PA-RISC Linux list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Something broke dselect/apt...
Date: Thu, 21 Jun 2001 16:26:24 +0100 [thread overview]
Message-ID: <20010621162624.M11438@linuxcare.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0106210628050.23440-100000@devnull.alaskatech.org>; from tom@Alaskatech.org on Thu, Jun 21, 2001 at 06:37:44AM -0800
On Thu, Jun 21, 2001 at 06:37:44AM -0800, Tom wrote:
> Unfortunately I wasn't watching the update - it's been a little too stable
> lately, I guess...
>
> I ran apt-get update/upgrade on Monday - all working. Just ran it again
> this morning, had ~9 packages updated. All updated fine - no errors on the
> update - but then apt-* fails to work with "error while loading shared
> libraries - /usr/lib/libapt-pkg-libc6.2-3.so.3.2: undefined symbol:
> _cp_push_exception". Trying to run dselect gives "error while loading
> shared libraries: dselect: undefined symbol: __rethrow".
>
> Has anyone noticed this yet and/or noticed something I may have goofed up?
> I believe there was a palo update in there, plus one of the libc6-*
> packages, but other than that I've no idea...
This is because you have picked up a new libstdc++3, but not a new apt.
We tried to update both together, but in the event, apt got delayed by
a day. You need to grab the new apt.deb and install with dpkg -i.
It should appear in <ftp://ftp.debian.org:/debian/pool/main/a/apt/>
in a few hours.
Richard
next prev parent reply other threads:[~2001-06-21 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 14:37 [parisc-linux] Something broke dselect/apt Tom
2001-06-21 15:26 ` Richard Hirst [this message]
2001-06-22 2:00 ` Tom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010621162624.M11438@linuxcare.com \
--to=rhirst@linuxcare.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tom@Alaskatech.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox