Bill, since my similar experience, I've seen plenty of other posts about the same thing. Thanks go to Joey for responding, although I agree that his answer is a little terse. What I take from it is that 1) that's what unstable is all about--needing to be prepared for some weirdness here and there, and 2) this is bug-related, i.e., the procedure you followed was correct, and the bug bit you, and getting out of it gracefully is purely a function of your experience and instinct with apt/dselect.
However--and this is my main point--I, and I'm guessing plenty of others like me who feel like we're seasoned enough to start running unstable but got bit by this sort of problem, really would like to hear from some folks who have done recent upgrades to woody and had to resolve this stickiness. I certainly don't have any problem with learning by jumping in feet first--probably wouldn't be here if I didn't--but this one seems tough enough, confirmed by several others, that I think it would be really helpful if someone out there more experienced can tell us if there's really a systemic problem, if there was an easy way around, or if we just ignorantly did something wrong. 8) I'm certainly not upset about this. After reinstalling my system I set up LILO again to boot my NT partition, and it still looked as heinous as it ever has. 8) The best things in life are free, eh? TIA! > Joey Hess <[EMAIL PROTECTED]> writes: > > Bill Wohler wrote: > > So file some bug reports, that's what the debian bug tracking system is > > for, and that's what testing is for too -- so people can test it and > > tell us what's broken/ > > Hey Joey, where I could identify the package, I have done so. > Unfortunately, in the case of the dependencies, I'm just so > overwhelmed that I have absolutely no idea how to identify which > packages have problems. > > Are there any tools that allow you to answer the question: Why did > the update of these 100 packages cause these 30 perfectly good > packages to get removed? This task is impossible to do by hand. > > Because so many X packages were affected, and because the debs were > just plain GONE from woody, I suspect a problem with the process > that migrates packages to woody. There's no "package" per se to > report problems with that, is there? Hence my message to debian-user > to alert the caretaker of the big woody that something was afoot at > the Circle-K. > > > > (in cleanup) Can't call method "DESTROY" on an undefined value at /usr/lib/perl5/Debian/DebConf/Question.pm line 251 during global destruction. > > > (in cleanup) Can't call method "close" on an undefined value at /usr/lib/perl5/Debian/DebConf/ConfModule.pm line 476 during global destruction. > > > > Don't bother filing a bug on this though, it's totally innocuous and > > fixed in unstable. > > Thanks for letting me know. That was in debconf? > > -- > Bill Wohler <[EMAIL PROTECTED]> http://www.newt.com/wohler/ GnuPG ID:610BD9AD > Maintainer of comp.mail.mh FAQ and mh-e. Vote Libertarian! > If you're passed on the right, you're in the wrong lane. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
