Bill Wohler wrote:
> 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.
It's helpful to turn on apt's problems resolver output.
-o Debug::pkgPro
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,
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.
U
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/
Bill Wohler wrote:
> (in cleanup) Can't call method "DESTROY" on an undefined value at
> /usr/lib/perl5/Debian/DebConf/Questi
If you are thinking of upgrading to woody, don't. At least, not
right now.
My first question: where are all the X packages in woody? Why all
the broken dependencies? When can we crawl out of our holes?
I replaced potato with woody in /etc/apt/sources.list, ran apt-get
update, and then
5 matches
Mail list logo
