On Sun, Oct 31, 2010 at 02:14:10PM +0100, Bastian Blank wrote: > On Sun, Oct 31, 2010 at 12:52:22PM +0100, Serafeim Zanikolas wrote: > > With Aptitude::ProblemResolver::Remove-Level=maximum, the picture is very > > different: > > 0 packages upgraded, 375 newly installed, 0 to remove and 21 not > > upgraded. > > As I wrote already, I see this as defeating the point of tasksel, and would > > suggest the first approach (run aptitude in simulation mode, and ask user > > confirmation about pending pkgs removal). > Did you check what the difference is? Does it just refuse to update > several packages? Both are valid solutions for the problem.
Also you checked on a not up-to-date system, tasksel should never need to upgrade things. Did you ask the aptitude people that the solution will be stable over several invocations? Bastian -- Phasers locked on target, Captain. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101031132710.gb32...@wavehammer.waldi.eu.org
