>From: Daniel Burrows <[EMAIL PROTECTED]>
> On Wednesday 22 June 2005 02:08 am, Elliott Mitchell wrote:
> > I'm doing a update from what is now oldstable to stable, using Aptitude's
> > interactive mode. There are a number of cases where Aptitude's dependancy
> > resolution likes to select packages that are unneeded. Sometimes these
> > selections even cause packages that were not otherwise broken to be put
> > in a broken state!
>
> The code that's causing problems is not in aptitude, it's in apt (the core
> libraries). You're right that this has various problems, but the solution is
> not necessarily as simple as just using mark-sweep, because of conflicts and
> versioned dependencies. Some of your diagnoses of individual cases seem
> unlikely to me, but that's actually not really relevant (see next
> paragraph :) ).
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.
--
(\___(\___(\______ --=> 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]
