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.
