On Thu, 23 Aug 2007 14:13:34 +0000, Kai-Martin Knaak wrote:

> On Thu, 23 Aug 2007 04:15:52 -0700, Rodney wrote:
>
>> Did you read the release notes for Etch previous to starting the
>> upgrade? And, did you follow the procedure in those release notes?
>
> <blush>Ok, you got me red handed </blush> I overestimated the ability of
> "apt-get dist-upgrade" to deal with this kind of problems.
>
> What can I do to dig me out of this hole? Use apt-get with some --force
> options? Build a local kernel image from source? Use the GUI interface of
> aptitude to manually select what packages to install?
>
> ---<(kaimartin)>---

I'm sorry I can't give you a definitive answer about this. You asked for a
hint and I thought by reading through the release notes you might be able
to determine what might work for the situation that your system got into.

You could try to do the dreaded "downgrade" to get back to a sarge install
(or something close) and start again but as poster Paul Cupis mentioned
about the testing lines, it looks like you weren't running a pure sarge
system anyway. Make sure you don't have anything pinned that could be
getting in the way of the package manager's ability to work. Slogging
through this manually may be what you end up doing, with a harsh but
useful lesson for the next release.

How customised is your system, you could save your /home and do a fresh
install of etch (possibly on a different partition) and then spend the
time to reconfigure anything that needs it. But manually dealing with that
libc6 issue might be enough. Paul Cupis's advice is probably what I
would try first. I truly wish you good luck.

Note: If you have been using apt-get all along, there usually are issues
with switching to aptitude. What you have to do is "keep all" first but
I don't think that would be advised at this point. It seems the
Debian developers have decided that Aptitude is the future, so I think we
might as well become familiar with it.