At 2007-01-23T17:30:25+1300, Volker Kuhlmann wrote: > You are hitting the nail square on the head here. It's set to stable (both > systems), but changing it to testing makes the aptitude install work just > fine!
> Looks like it's a question of pushing the dependency resolver into setting > different priorities. If you want to keep the system running stable and only pull in specific packages from testing, you can leave it set to stable, and then install packages like so: # aptitude -t testing linux-image-2.6.18-3-486 This will select linux-image-2.6.18-3-486 and its dependencies from testing, but only those where the versions in stable are not recent enough. With this sort of configuration, upgrade/dist-upgrade and the like will continue to pull packages from stable. It'll also generally continue to upgrade the packages installed from testing, depending on what's also happening in stable with that package, etc. There's a good explanation of the priority system and why things behave the way they do here[0]. If you change the default version to testing, it will consider all packages in testing to be appropriate to upgrade to, and the next upgrade/dist-upgrade you run will turn your stable install into a testing install. > Btw when doing this on a running system, grub's menu.lst isn't updated, > but on a new install it just installs the new kernel and a corresponding > menu.lst. update-grub(8) and kernel-img.conf(5) are responsible for this. It should be run automatically every time a new kernel is installed (and is definitely run when performing this kernel upgrade on a pristine sarge install). Not sure why it didn't run in your case. Check /etc/kernel-img.conf to see if update-grub is configured to run for the postinst and postrm hooks. [0] http://www.argon.org/~roderick/apt-pinning.html Cheers, -mjg -- Matthew Gregan |/ /| [EMAIL PROTECTED]
