On Fri, Aug 15, 2003 at 10:44:26PM -0600, Jason Gunthorpe wrote: > Yes this is the problem. > > While flailing about looking for any solution that works it stops when it > finds the first solution. > > There is some code that does some simple things to minimize extra packages > but it cannot handle very complex relationships between the extra > packages. I'm actually not sure if it is engaged for this particular code > path or not > > Fundamentaly these sorts of problems are not truely solvable. The problem > is NP (a varietion of 3 sat) and thus cannot be perfectly solved. The > heuristics are designed around common idioms that were in place around the > hamm release - since then people have created dependency networks of ever > increasing complexting and it now the limits show up alot more often.
Thanks for the explanation. Since this situation would seem to only be possible when removing a package while the system is not up-to-date with available packages, I'm not particularly concerned about this behaviour. -- - mdz

