As a follow-up to my earlier tests, if you hit aptitude over the head to force its resolver to behave more safely on package installation, then the first thing it offers to do is fine.
Having reverted the VM used in the earlier tests to a lenny snapshot: # aptitude --safe-resolver install linux-image-`uname -r | sed 's, [^-]*-[^-]*-,,'` The following NEW packages will be installed: firmware-linux-free{a} libdb4.7{a} libuuid-perl{a} linux-base{a} linux-image-2.6.32-5-686{a} linux-image-686 The following packages will be upgraded: libuuid1 perl perl-base perl-modules The following packages are RECOMMENDED but will NOT be installed: uuid-runtime 4 packages upgraded, 6 newly installed, 0 to remove and 199 not upgraded. Need to get 36.6MB of archives. After unpacking 81.0MB will be used. Do you want to continue? [Y/n/?] which is exactly what is wanted. The same behaviour is seen with both the lenny and squeeze versions of aptitude. Presumably the same could be achieved by fiddling with aptitude's scores or levels until it did the right thing with whatever resolver it is using for an install request. regards Stuart (who wonders if he should clone this bug over to aptitude too...) -- Stuart Prescott www.nanoNANOnano.net
signature.asc
Description: This is a digitally signed message part.