On Tue, Nov 29, 2005 at 07:40:25AM +0100, Marc Haber <[EMAIL PROTECTED]> was heard to say: > On Mon, Nov 28, 2005 at 05:09:11PM -0600, Daniel Burrows wrote: > > On Mon, Nov 28, 2005 at 11:42:59PM +0100, Marc Haber <[EMAIL PROTECTED]> > > was heard to say: > > > On Mon, Nov 28, 2005 at 04:35:00PM -0600, Daniel Burrows wrote: > > > > On a second look at this bug report, I think I may have misunderstood > > > > it the first time I skimmed over it. The bug is not that the solution > > > > suggested is incorrect, but that the dependencies should be resolved > > > > without prompting in this case, right? > > > > > > Yes. Also, only one round of resolution is done, so it takes multiple > > > invocations with the same command line to have all packages and all > > > dependencies installed. This is particularly annoying with big > > > packages like build-depends. > > > > I'm not sure what you mean about one round of resolution. I can reproduce > > this exactly [0] if I set Aptitude::Auto-Install=false (either via -o or in > > a > > configuration file), which is why I was asking about ~/.aptitude/config. > > When > > I accept the suggested solution, I get a consistent result. > > In fact, Auto-Install=false is set in _all_ my .aptitude/config files > on _all_ my unstable systems which I am pretty sure I didn't manually > do, at least not in the last few days. Commenting out the line setting > it to false fixes the problem for me.
In that case, it's expected behavior (aside from it getting set to false, of course). Aside from editing the file manually, all that I know of that would do this is deactivating the "automatically resolver dependencies of a package when it is selected" option in the Options -> Dependency Handling dialog. Daniel
signature.asc
Description: Digital signature
