>From: Daniel Burrows <[EMAIL PROTECTED]>
> On Wednesday 22 June 2005 07:30 pm, Elliott Mitchell wrote:
> > I don't know the code layout, so I can't comment on that.
> >
> > The four cases are *very* real. I mentioned I was doing this over a
> > couple sessions. Pretty much I quit for the night, and then start
> > Aptitude again when I can. Every time I restart, it has tried to fix
> > those four packages, which aren't broken; and all the packages it wants
> > to add would break other things.
> >
> > The dependancy resolution code must be doing something pretty stupid to
> > try to add unneeded packages and break other packages.
>
> Okay, I can reproduce this now. The problem is a funny interaction between
> the code that restores package states and the apt recursive resolver. I'll
> have to see what the best way of resolving this is -- just doing the initial
> marks with recursive resolution turned off is probably best IMO.
I suppose it could be. I was guessing state saving was fine, as most were
fine, just those four.
> If you'd mentioned the bit about quitting and restarting the program
> originally, you could have avoided a long and tedious lecture on problem
> resolution ;-).
"I'm having to take care of this over a number of sessions". See the
above for why I didn't place emphasis on this point.
--
(\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/)
\BS ( | [EMAIL PROTECTED] PGP 8881EF59 | ) /
\_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/
\___\_|_/82 04 A1 3C C7 B1 37 2A*E3 6E 84 DA 97 4C 40 E6\_|_/___/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
