On Sun, 23 Nov 2014, Luca Capello wrote: > while installing a new Debian wheezy following our internal > instructions[1] that worked flawlessly in the past, I was quite > surprised by the error message about not supported kernel appeared > during the intel-microcode installation.
... > 1) the default apt-listchanges/which debconf value is news, which means > that on upgrades the above message is not shown, instead it should > have been added to debian/NEWS. It *is* in NEWS.Debian. However, it won't work right for the backported package because the version heading in the NEWS file does not end with a "~". I will fix that. And I am likely to file a bug on apt-listchages, too: it shouldn't be skipping entries it didn't display previously just because they are "in the future". > 2) AFAIK, if a backport package needs a feature of another backport > package to work on a stable installation, than the second package > should be a Depends:. That I can't do. This is a runtime dependency on the kernel version you're building the initramfs *for*. It is not even related to whatever kernel you're running at the time the initramfs is built. If you don't need any of the features in the backported intel-microcode package, why were using it instead of the stable package? early microcode update support is the whole *point* of the backported package... > Versions of packages intel-microcode recommends: > ii initramfs-tools 0.109.1 This is going to be a problem as well. I will consider switching to a Depends. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
