On Thu, Nov 14, 2002 at 08:40:22PM -0800, Paul Mackinney wrote:
> > # dpkg -i --force-downgrade /var/cache/apt/archives/libstdc++2.10-glibc2.2_1%3a2.95.4-12_i386.deb
> In general I knew that this was an option, but of course 'man dpkg' was
> one of the commands that failed...
I'm fairly sure that man is written in C.
rob@thebox> ldd /usr/bin/man
libc.so.6 => /lib/libc.so.6 (0x4001f000)
libdb3.so.3 => /usr/lib/libdb3.so.3 (0x40133000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
> > why run unstable, which is _intended_ as a
> > place for leading-edge testing -- "catch it here before it breaks
> > something really important" -- if you aren't able to deal with the
> > problems that sooner or later _will_ arise?
> Like many other people, I started running unstable because Potato was
> hopelessly out of date and Woody felt very stale. I've stuck with it
> since the Woody release because I don't feel much like downgrading my
> system. But I also believe that running unstable means that I've agreed
> to ride out the bumps without squawking.
You could always switch your source.list to sarge and gradually drift down to
it.
-rob
Attachment:
pgp1fG9530qJv.pgp
Description: PGP signature