Re: kernel abiname transition and security updates status
On Wed, Feb 16, 2005 at 09:00:53PM -0500, Joey Hess wrote: After 1.5 months of mails, I guess this will be the last such mail sent to the kernel team. However, I understand that some new security hole may need yet another kernel ABI change. If that's true, the sooner we find out about that the better, though judging from experience, updating to a -3 abi will be long and painful. The following arches still need to have their kernels updated: i386 Argh, the speakup kernels are not updated. Wish I'd thought of that earlier. :-( I have CCed the maintainer as I am not sure if he is on either of these lists. In any case that kernel seems well over due for an update. arm Still not updated. I don't think there are any arm people hanging out on debian-kernel either. If you work out how to contact them, please let us know. powerpc 2.4 still not updated. My plan continues to be to go ahead and release d-i rc3 without these updates, unless someone wakes up and does them. Since none of the remaining kernels have abinames, updated debs could even be slipped into sarge after rc3 without a lot of fuss (aside from broken third party modules and what have you). On the d-i side, this is the current situation: (Note that this table is currently being used to track the status of the d-i sarge branch as well as trunk, and values represent both unless otherwise noted.) rootskel and arch udebs[0]build/config[1] base-installer debian-cd i386 2.4.27-2/2.6.8-2[2] 2.4.27-2/2.6.8-2 2.4.27-2/2.6.8-2 2.4.27-2/2.6.8-2 alpha2.4.27-22.4.27-2 2.4.27-2 2.4.27-2 amd64not tracking currently arm[8] 2.4.27 2.4.27none [5] hppa[3] 2.6.8-2 2.6.8-2 2.6.8-2 2.6.8-2 ia64 2.4.27-2/2.6.8-22.4.27-2/2.6.8-2 2.4.27-2/2.6.8-2 2.4.27-2/2.6.8-2 m68k 2.2.25/2.4.27 2.2.25/2.4.27 2.2.25/2.4.27 mips 2.4.27 2.4.272.4.27 mipsel 2.4.27 2.4.272.4.27 powerpc 2.4.27/2.6.82.4.27/2.6.8 2.4.27/2.6.8 2.4.27/2.6.8 [9] apus 2.4.27 2.4.27 2.4.27 none [6] s390 2.4.27-22.4.27-1 [4] 2.4.27-2 N/A sparc2.4.27-2/2.6.8-22.4.27-2/2.6.8-2 2.4.27-1/2.6.8-2 [7] [0] none of the updated udebs are in sarge yet, plan is to push them all in in preparation for rc3 [1] not yet updated to -2 kernels in sarge branch; plan is to sync all build/ changes to sarge in one go [2] speakup kernel flavour not yet updated [3] hppa 2.4 is dropped, still a few vestiges of it here and there, including some stuff in base-installer and the udebs [4] Update needed, but daily builds down.. [5] I checked and the arm netinst CD really has no kernel deb on it at all! [6] did not see any apus kernels on the powerpc netinst CD [7] 2.4.27-1 kernels have not yet reached sarge [8] arm kernels are not updated with security fixes [9] powerpc 2.4 kernels are not updated with security fixes So we're really quite close now to being able to release rc3 from the kernel update standpoint at least. -- see shy jo -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel abiname transition and security updates status
* Horms [EMAIL PROTECTED] [2005-02-22 19:44]: arm Still not updated. I don't think there are any arm people hanging out on debian-kernel either. If you work out how to contact them, please let us know. Vince has uploaded new images (built against kernel source -8) today. I'm currently preparing udebs. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel abiname transition and security updates status
After 1.5 months of mails, I guess this will be the last such mail sent to the kernel team. However, I understand that some new security hole may need yet another kernel ABI change. If that's true, the sooner we find out about that the better, though judging from experience, updating to a -3 abi will be long and painful. The following arches still need to have their kernels updated: i386 Argh, the speakup kernels are not updated. Wish I'd thought of that earlier. :-( arm Still not updated. powerpc 2.4 still not updated. My plan continues to be to go ahead and release d-i rc3 without these updates, unless someone wakes up and does them. Since none of the remaining kernels have abinames, updated debs could even be slipped into sarge after rc3 without a lot of fuss (aside from broken third party modules and what have you). On the d-i side, this is the current situation: (Note that this table is currently being used to track the status of the d-i sarge branch as well as trunk, and values represent both unless otherwise noted.) rootskel and arch udebs[0]build/config[1] base-installer debian-cd i386 2.4.27-2/2.6.8-2[2] 2.4.27-2/2.6.8-2 2.4.27-2/2.6.8-2 2.4.27-2/2.6.8-2 alpha2.4.27-22.4.27-2 2.4.27-2 2.4.27-2 amd64not tracking currently arm[8] 2.4.27 2.4.27none [5] hppa[3] 2.6.8-2 2.6.8-2 2.6.8-2 2.6.8-2 ia64 2.4.27-2/2.6.8-22.4.27-2/2.6.8-2 2.4.27-2/2.6.8-2 2.4.27-2/2.6.8-2 m68k 2.2.25/2.4.27 2.2.25/2.4.27 2.2.25/2.4.27 mips 2.4.27 2.4.272.4.27 mipsel 2.4.27 2.4.272.4.27 powerpc 2.4.27/2.6.82.4.27/2.6.8 2.4.27/2.6.8 2.4.27/2.6.8 [9] apus 2.4.27 2.4.27 2.4.27 none [6] s390 2.4.27-22.4.27-1 [4] 2.4.27-2 N/A sparc2.4.27-2/2.6.8-22.4.27-2/2.6.8-2 2.4.27-1/2.6.8-2 [7] [0] none of the updated udebs are in sarge yet, plan is to push them all in in preparation for rc3 [1] not yet updated to -2 kernels in sarge branch; plan is to sync all build/ changes to sarge in one go [2] speakup kernel flavour not yet updated [3] hppa 2.4 is dropped, still a few vestiges of it here and there, including some stuff in base-installer and the udebs [4] Update needed, but daily builds down.. [5] I checked and the arm netinst CD really has no kernel deb on it at all! [6] did not see any apus kernels on the powerpc netinst CD [7] 2.4.27-1 kernels have not yet reached sarge [8] arm kernels are not updated with security fixes [9] powerpc 2.4 kernels are not updated with security fixes So we're really quite close now to being able to release rc3 from the kernel update standpoint at least. -- see shy jo signature.asc Description: Digital signature
Re: kernel abiname transition and security updates status
* Steve Langasek wrote: On Fri, Feb 04, 2005 at 04:05:41PM -0500, Joey Hess wrote: alpha Kernel updated, but not yet in testing; udebs not yet updated (I thought they were before, but was wrong). Kernel is in testing, udebs are updated;; but the alpha debs need another revision because 2.4.27-6 pushed ext2 out as a module and makes the d-i initrds fail. Sorry, my fault, 2.4.27-7 is currently compiling. Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel abiname transition and security updates status
Steve Langasek wrote: hppa 2.4 now updated, but we dropped it. 2.6 has abiname; still not updated, update is in kernel team svn. [This is likely to block d-i rc3 until the new hppa 2.6 kernels with the new abiname are available.] Updated 2.6.8 in sid, needs an ftp-master to do binary removals yet before it can propagate to testing. Are there udebs available yet? Removals should be done. I'm uploading the udebs, though I haven't tested them yet and the 32 bit kernel seemed to have lots of changes (dropped modules, modules with changed dependencies on other modules). sparc 2.6 updated to -2 abiname; 2.4 not updated (except in svn); 2.6 debs not yet in testing (due to RC #288180); udebs updated. I think the 2.6 debs hit testing today. [This is likely to block d-i rc3 until the new sparc 2.4 kernels with the new abiname are available.] 2.4 on sparc is still the big blocker. No updated kernel-images are available yet. This is a real problem. I haven't seen joshk around lately and AFAIK he's the only person we have working on sparc kernels. -- see shy jo signature.asc Description: Digital signature
Re: kernel abiname transition and security updates status
On Fri, Feb 04, 2005 at 04:05:41PM -0500, Joey Hess wrote: Joey Hess wrote: Before we can release d-i rc3 we need all the kernels updated with at least some security fixes, notably the ones that change the kernel module ABI, and we need to update things to reflect the new kernel abiname. Here's my understanding of the current status of that: Update again, it's now been about 1 month since my first mail. alpha Kernel updated, but not yet in testing; udebs not yet updated (I thought they were before, but was wrong). Kernel is in testing, udebs are updated;; but the alpha debs need another revision because 2.4.27-6 pushed ext2 out as a module and makes the d-i initrds fail. hppa 2.4 now updated, but we dropped it. 2.6 has abiname; still not updated, update is in kernel team svn. [This is likely to block d-i rc3 until the new hppa 2.6 kernels with the new abiname are available.] Updated 2.6.8 in sid, needs an ftp-master to do binary removals yet before it can propagate to testing. Are there udebs available yet? sparc 2.6 updated to -2 abiname; 2.4 not updated (except in svn); 2.6 debs not yet in testing (due to RC #288180); udebs updated. [This is likely to block d-i rc3 until the new sparc 2.4 kernels with the new abiname are available.] 2.4 on sparc is still the big blocker. No updated kernel-images are available yet. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: kernel abiname transition and security updates status
On Fri, Feb 04, 2005 at 04:05:41PM -0500, Joey Hess wrote: powerpc No abiname. 2.4 not updated. 2.6 updated, debs in testing; udebs updated. [If powerpc 2.4 is not updated with the security fixes soon, I will probably not let it block a d-i rc3 release.] Oh well, whatever is going to be decided now. I hear that we may go with 2.6.10, and that i should prepare 2.6.10 packages asap, and then finally not once i am done with it. If we could drop 2.4 kernels on powerpc, i would be happy, but i fear we cannot do that, i will do new powerpc 2.4 kernels nextly. What exactly is the timeframe for rc3 anyway ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel abiname transition and security updates status
Joey Hess wrote: Before we can release d-i rc3 we need all the kernels updated with at least some security fixes, notably the ones that change the kernel module ABI, and we need to update things to reflect the new kernel abiname. Here's my understanding of the current status of that: Update again, it's now been about 1 month since my first mail. alpha Kernel updated, but not yet in testing; udebs not yet updated (I thought they were before, but was wrong). amd64 Updated, but I'm not tracking this arch. arm No abiname; not updated. [At the moment this is one of the arches that I'd consider releasing d-i rc3 without it being updated for the kernel security fixes, since it has no abiname, and since the daily builds have been down since October.] hppa 2.4 now updated, but we dropped it. 2.6 has abiname; still not updated, update is in kernel team svn. [This is likely to block d-i rc3 until the new hppa 2.6 kernels with the new abiname are available.] i386 2.4 and 2.6 updated to -2 abiname; debs in testing; udebs updated. ia64 2.4 and 2.6 updated to -2 abiname; debs in testing; udebs updated. m68k No abiname; debs updated and in testing (for 2.4; dunno about 2.2); udebs updated. mips No abiname. Kernel updated and in testing; udebs updated. mipsel No abiname. Kernel updated and in testing; udebs updated. powerpc No abiname. 2.4 not updated. 2.6 updated, debs in testing; udebs updated. [If powerpc 2.4 is not updated with the security fixes soon, I will probably not let it block a d-i rc3 release.] s390 Just fixed; debs not yet in testing; udebs updated. sparc 2.6 updated to -2 abiname; 2.4 not updated (except in svn); 2.6 debs not yet in testing (due to RC #288180); udebs updated. [This is likely to block d-i rc3 until the new sparc 2.4 kernels with the new abiname are available.] So hppa and sparc are the only remaining blockers from the debian-kernel side for the d-i release, though powerpc 2.4 and arm also still really need updates. And on the d-i side we still need to update the alpha udebs, update rootskel and base-installer and the build system to use the new abinames where appropriate, update debian-cd, and make sure it all works. -- see shy jo signature.asc Description: Digital signature
Re: kernel abiname transition and security updates status
* Joey Hess wrote: Update again, it's now been about 1 month since my first mail. alpha Kernel updated, but not yet in testing; udebs not yet updated (I thought they were before, but was wrong). Steve uploaded an updated linux-kernel-di-alpha package today. Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel abiname transition and security updates status
On Thu, Jan 20, 2005 at 04:13:17PM -0500, Joey Hess wrote: powerpc No abiname. 2.4 not updated. 2.6 updated, debs in testing; udebs updated. [If powerpc 2.4 is not updated with the security fixes soon, I will probably not let it block a d-i rc3 release.] Ah, well, i really need to do the build, and this WE seems the perfect moment for that :) That said, even if 2.4 is not updated, it doesn't seem all that problematic for rc3, since powerpc defaults to 2.6 anyway, and the only reason i see of keeping 2.4 is for the powerpc miboot oldworld floppies. Current situation is : pmac newworld : both 2.4 and 2.6 works, 2.6 is prefered. pmac oldworld - miboot : 2.4 works for sure (could it install a 2.6 kernel ?) 2.6 works some times and other not in an undeterministic way. = that said, the rc releases are built from sarge, and thus without miboot anyway, right ? pmac oldworld - bootx : 2.4 and 2.6 work, 2.6 works perfectly. pmac oldworld - coff OF booting : no real idea about this one. only 2.6 i think. prep : only 2.6 kernel work. pegasos2 : both 2.4 and 2.6 work, 2.6 is preffered, has been ages since i did a 2.4 test pegasos1 : saddly need a 2.4 kernel as the 2.6 initrd is too big. I hope to have an OF update soon though. chrp/ibm-rs6k - powerpc : am not aware of 2.4 report, 2.6 works. chrp/ibm-rs6k - power3 : am not aware of 2.4 report, probably won't work, 2.6 works. chrp/ibm-rs6k - power4 : am not aware of 2.4 report, probably won't work, 2.6 works. pmac newworld G5 : 2.6 is needed. apus : 10 machines left, but only 2.4 for now. pmac nubus : not yet supported, some unofficial builds, 2.4 build only On a side note, an upload of prep-installer will propulse the prep subarch to fully supported status. prep-installer needs some work though. Hope this helps, Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel abiname transition and security updates status
On Fri, Jan 14, 2005 at 08:41:26PM +0900, Horms wrote: On Thu, Jan 13, 2005 at 04:24:36PM +0900, Horms wrote: On Mon, Jan 10, 2005 at 10:27:20PM +, Martin Michlmayr wrote: * Joey Hess [EMAIL PROTECTED] [2005-01-10 16:24]: As far as I know, no other arches except amd64 (not tracking that) are mips and mipsel have been updated. However, given the new local root exploit (fixed in SVN), we'll all need to make another round of updates anyway. Josh Kwan and I chatted about this yesterday on IRC. He and I are both pretty happy with kernel-source-2.4.27 as it is, but I would like a chance to go through recent bug reports just to make sure there isn't anything missing. As a result we are aiming to release next week. Sorry for this taking a bit longer than I had hoped. I now have kernel-source-2.4.27 in a state where I am happy to release it as 2.4.27-8. I have made both kernel-source-2.4.27 and kernel-image-2.4.27-i386 up on http://debian.vergenet.net/pending/ for people to take a look at. I aim to releaase these verbatim tomorrow if there are no objections. If you make an updates to SVN please drop me an email, so I make sure that they make it in. As I am not intending to rebuild again. If you put [EMAIL PROTECTED] in To or CC then it will go to the top of my mail-reading priority list. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel abiname transition and security updates status
Horms wrote: [snip] I have made both kernel-source-2.4.27 and kernel-image-2.4.27-i386 up on http://debian.vergenet.net/pending/ for people to take a look at. Builds fine for mips, images soon available at http://people.debian.org/~ths/mips-kernels/kernel-patch-2.4.27-mips/ Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel abiname transition and security updates status
Christian T. Steigies wrote: [snip] I uploaded new 2.6.8 kernel-images for m68k a week ago, but I did not make it urgent...: Too young, only 7 of 10 days old For 2.4.27 I am waiting for the latest kernel-source to be released before I build new images. This is supposed to happen today/tomorrow? I should be able to get those images ready over the weekend then, and I'll try to remember to make it more urgent... Supposed-to-be final kernel-source can be found at http://debian.vergenet.net/pending/ I have no idea about the abichanges, m68k uses no abiname? Is that a problem? Is there anything else m68k has to do, like build new d-i-k-i-m68k packages? Anything else I am missing? External modules, as well as modules separated out for d-i, will break, so they need to be kept in sync. IOW, needs new d-i-k-i-m68k, preferably uploaded at the same time than the new kernel, and also updated external modules if there are any. Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel abiname transition and security updates status
On Thu, Jan 20, 2005 at 11:11:14PM +0100, Christian T. Steigies wrote: I have no idea about the abichanges, m68k uses no abiname? Is that a problem? The downside of not includeing an abiname in the package name is that past d-i releases will break once the updated kernels and udebs reach testing. So they not yet released d-i releases break on the most popular arch of the early nineties. Does anybody care? If there were abinames in the m68k package (-1, -2, ... added to the package name?), would we create a new package for every abichange? Doesn't that contradict the plan of d-kernel to reduce the number of kernel-packages? The point of using an abiname in your package naming is that you're assured (barring bugs) that all kernel modules in your search path are compatible with that kernel version. If you use /lib/modules/2.4.27-$subarch instead of /lib/modules/2.4.27-$abiname-$subarch, you have no mechanism for coping with version skew when a Debian revision includes a change to the public interfaces used by modules. It does not contradict the plans for keeping the kernel package count down, because you don't get to keep both ABI versions around -- you don't want the old one *anyway*, because it has security bugs. In any case, the source package names are kept the same and only the binary package names change, so you only ever get one of these in testing at a time. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: kernel abiname transition and security updates status
* Joey Hess wrote: Norbert Tretkowski wrote: Updated alpha packages were accepted a few hours ago. Do you or maybe vorlon plan to rebuild linux-kernel-di-alpha with them? I'll update the package tomorrow. Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel abiname transition and security updates status
Before we can release d-i rc3 we need all the kernels updated with at least some security fixes, notably the ones that change the kernel module ABI, and we need to update things to reflect the new kernel abiname. Here's my understanding of the current status of that: i386 2.4 and 2.6 updated to -2 abiname; debs not yet in testing; udebs updated. Until debs hit testing we cannot change rootskel/base-installer to use the new package names. ia64 Now same as i386. powerpc No abiname. 2.4 not updated(?). 2.6 updated, udebs updated, debs not yet in testing. As far as I know, no other arches except amd64 (not tracking that) are updated. Of the other arches, alpha, hppa (2.6), s390, and sparc have a abiname field in the kernel package names, so we really must wait on those before releasing rc3. arm, m68k, hppa (2.4), mips, and mipsel have no abinames, which just means past d-i releases will break even worse for those arches once the updated kernels and udebs reach testing. So I'd like to delay rc3 until those are updated with the abi changes too, to avoid having rc3 break after it's released. Anyway, I hope we can get the new kernels and udebs built for the missing arches in the next couple of weeks? -- see shy jo signature.asc Description: Digital signature
Re: kernel abiname transition and security updates status
* Joey Hess [EMAIL PROTECTED] [2005-01-10 16:24]: As far as I know, no other arches except amd64 (not tracking that) are mips and mipsel have been updated. However, given the new local root exploit (fixed in SVN), we'll all need to make another round of updates anyway. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
