Craig Dickson declaimed: > It's unfortunate that this happened, but this is unstable, and > developers aren't perfect. I'm actually less disturbed that this > happened than that so many people have posted desperate "please help" > messages about it, That was sort of my point. I looked for a message on the topic before posting myself or filing a bug report and the answer was right there.
> I mean, seriously, let's look at the process in detail... This was very helpful, thank you. > Or you could try to just back out of the > problem like this: > > # 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... > 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. Thanks for your post, I appreciated reading your point of view and gaining the benefit of your troubleshooting process, not to mention reading everyone else's reactions to your ideas. Regards, PM -- Paul Mackinney [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
