Hi Henrique, On Thu, 27 Nov 2014 14:05:25 -0200, Henrique de Moraes Holschuh wrote: > On Sun, 23 Nov 2014, Henrique de Moraes Holschuh wrote: > > 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 have tested this, and apt-listchanges *did* display the NEWS entry on > upgrade both from the stable version, and the previous backported version.
My fault, I was thinking something and writing another thing: it should have been "which means that on *new installations* the above message is not shown". > But this thing is known to be flaky, and the test procedure requires > removing the apt-listchanges database (which could easily defuse a bug), so > I will repload with a "bumped" version in the NEWS file in hope that it will > ensure more people gets the warning. Thank you. > > > 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. Exactly because it is not related to the kernel you are running, but on *at least* one kernel package installed IMHO it is an hard Depends: for Debian. > > 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... IMHO there are two problems in your reasoning: first, how do I know if I need any of the features in the backported package? If I have to manually check them *before* installing the package I do not see why I would use the Debian package at all. Second, the previous backported package worked with no problems, it is the new version that actually stopped working ;-) To solve both problems there should be a way to say: look, you are installing a package that requires a newer kernel version... > > > 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. > > I've switched to a depends for backports, I can undo this easily if it > causes problems. Unstable and stable will remain with a recommends. Thank you very much! However, this does not seem to automatically pull a backported kernel: ===== # apt-get update [...] # apt-get install -d -t wheezy-backports initramfs-tools Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: initramfs-tools 1 upgraded, 0 newly installed, 0 to remove and 32 not upgraded. Need to get 0 B/92.6 kB of archives. After this operation, 3,072 B of additional disk space will be used. [...] # ===== BTW, this is not the first time you are so supportive on one of the bugs I have reported, it is a pleasure to deal with you :-D Thx, bye, Gismo / Luca
signature.asc
Description: Digital signature