On Mon, Apr 09, 2007 at 04:30:27PM +0200, Loïc Minier <[EMAIL PROTECTED]> was
heard to say:
> pbuilder recently gained the ability to resolve build-deps by creating
> a fake .deb where this are regular deps and then invoking aptitude to
> "fix" it. This permits pbuilder to use the powerful aptitude
> dependency resolver! It works like a charm, but I've hit a case today
> while building experimental packages of epiphany-extensions where
> aptitude would consume huge amounts of CPU indefinitely, and I decided
> to stop aptitude when it was taking 750 MB of RAM.
Hrm, the resolver has a cutoff to stop thinking after "a while", but
it looks like you've overridden that (-y). Maybe I should add some
additional logic that aborts the search regardless of -y if the
resolver's data structures get too big (this means we have a problem
that's "too hard" to solve).
If there isn't a solution at all (which it sounds like is probably
happening in your case), I'd hope the resolver would be able to
accumulate enough conflicts to toss the whole problem out. I bet that
you have a cache with several copies of a large dependency tree (e.g.
in testing, unstable & experimental) and where some dependencies in
the tree can be satisfied from any repository but others conflict
across repositories. That's the hardest case for the resolver, and I
don't think it handles it very gracefully.
Could you add "-o Aptitude::CmdLine::Resolver-Debug=true" to the
aptitude command-line and send me the output?
Thanks,
Daniel
