Package: udev Version: 0.092-2 Severity: serious Tags: help Justification: Policy 3.9.1
Marco: filing this bug after discussion with our RMs, so that it stands out in the upcoming BSP, and someone sends you a patch implementing this idea that neither you nor i have time to implement. On sunday, i tried an upgrade from sarge to sid, and as thus hit the problem with the udev/kernel/hal&co upgrade loop. Currently this can be solved by touching a file which will bypass this question, and the upgrade script fails with this message. This is ugly and non-evident, and i passed the message altogether before first reading it (especially as it was in the middle of a 700+ package upgrade). I discussed this with Marco on irc, and he agreed that the right thing to do would be to use a debconf question instead of the current bit. Furthermore, policy mandates, for sarge already, that all user interaction be done using debconf, so this is RC anyway. So, the problem is that the new udev needs a kernel version 2.6.12 to be running, and fails altogether for 2.4 kernels. When detecting a 2.4 kernel is running, udev instaklls itself, but in disabled form. When detecting the sarge 2.6.8 kernel, udev refuses to install, and if you already had part of gnome upgraded, you are left with a mess. More detail can be found in Bug #349354: initramfs-tools - kernel -udev dependency loop Now, the proposed solution would be to ask this question in a debconf dialog, inform the user that he is running 2.6.8, and either abort (as is done now, and which stays the default), or continous the upgrade and in this case inform the user that he should make sure to install a 2.6.12 kernel or his system may well end up being unbootable. Marco, once the basic setup is in place, it would be best if you polished those dialogs to your convenience, or something, or added some toughts to this bug report, or discussed it with the BSPer directly or something. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
