On Wed, Oct 17, 2007 at 11:26:05AM +0300, Vitalie Lazu <[EMAIL PROTECTED]> was heard to say: > On Wednesday 17 October 2007, Daniel Burrows wrote: > > On Mon, Oct 15, 2007 at 04:08:33PM +0200, Loïc Minier <[EMAIL PROTECTED]> > > was heard to say: > > > On Mon, Oct 15, 2007, Vitalie Lazu wrote: > > > > > And isn't it what happened? Which build-deps were you missing in the > > > > > end? > > > > As you can see in my bug report output, I did not have libtool (>= > > > > 1.5-2) and automake1.9 > > > > > > /in the end/ you did have libtool and automake1.9 installed though. > > > > > > However after reading the install log again, I agree with Junichi that > > > this looks like an aptitude bug. I would suspect this is related to > > > the switch from aptitude to APT to handle automatically installed > > > dependencies. > > > > It looks to me like a bad pkgstates file generated by an old version > > of aptitude. Was this system originally installed as etch or sarge? > > > > Daniel > > > > First it was sarge, then I ugraded to etch/testing -> etch(stable) -> sid -> > lenny/testing
That's probably the problem, then. Old aptitudes (I think the sarge timeframe suffered from this) would sometimes decide that packages you had installed with other frontends were automatically installed. This shouldn't happen any more (mostly), but I can't fix state files that have already been corrupted. Running "aptitude keep-all" is one way to cancel all the spurious removals. Daniel
