hey, I'd like to announce our intent to proceed with rev'ing the ABI for the "sarge2" set of kernel security updates that the kernel team is currently preparing. There are at least 3 outstanding security issues[1] that would trigger an ABI change, two of which have been known since before r0.
As far as I can tell, an ABI change only breaks d-i if it is incorporated into a point release - updates to security.debian.org should be safe. We should therefore be able to move forward without impacting d-i, and begin work on the d-i update as soon as the security update is released. If I misunderstand, and we need synchronization at an earlier stage, please let me know. Any ETA for the sarge2 update would be artificial this early; but I'll keep you informed. [1] http://svn.debian.org/wsvn/kernel/patch-tracking/CAN-2005-0449?op=file&rev=0&sc=0 http://svn.debian.org/wsvn/kernel/patch-tracking/CVE-2005-3527?op=file&rev=0&sc=0 http://svn.debian.org/wsvn/kernel/patch-tracking/ia64-buggy-preempt?op=file&rev=0&sc=0 -- dann frazier <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
