Re: Timeline for r3

2006-07-09 Thread Frans Pop
On Sunday 09 July 2006 21:59, Frans Pop wrote: > Seems like the i386 packages have now made it in. Still missing: > - linux-kernel-di-arm > - linux-kernel-di-m68k > - linux-kernel-di-mips > - linux-kernel-di-mipsel > - linux-kernel-di-powerpc Oops. Did not look correctly: i386 is still missing too

Re: Timeline for r3

2006-07-09 Thread Frans Pop
On Friday 07 July 2006 18:31, Frans Pop wrote: > Most of the new kernel udeb packages are now in p-u, except for those > that did not have to go through NEW: [...] > Please approve these for p-u ASAP. Seems like the i386 packages have now made it in. Still missing: - linux-kernel-di-arm - linux-ke

Re: Timeline for r3

2006-07-08 Thread Martin Zobel-Helas
Hi, okay with me. On Fri, Jul 07, 2006 at 06:31:57PM +0200, Frans Pop <[EMAIL PROTECTED]> wrote: > On Friday 30 June 2006 23:08, Frans Pop wrote: > > Dann has today uploaded the kernel udeb packages for all arches, except > > for AMD64 (as that has not yet been released by the security team). >

Re: Timeline for r3

2006-07-07 Thread Frans Pop
On Friday 30 June 2006 23:08, Frans Pop wrote: > Dann has today uploaded the kernel udeb packages for all arches, except > for AMD64 (as that has not yet been released by the security team). > Most of them are currently in NEW, all need to be approved for proposed > updates. When that has happened,

Re: Timeline for r3

2006-07-01 Thread Steve McIntyre
On Fri, Jun 30, 2006 at 10:16:51AM -0600, dann frazier wrote: >On Fri, Jun 30, 2006 at 03:45:27PM +0100, Steve McIntyre wrote: >> On Thu, Jun 29, 2006 at 08:03:32PM +0100, Steve McIntyre wrote: >> >On Thu, Jun 29, 2006 at 12:13:08PM -0600, dann frazier wrote: >> >>On Thu, Jun 29, 2006 at 06:40:01PM

Re: Timeline for r3

2006-06-30 Thread Frans Pop
On Thursday 29 June 2006 18:40, Frans Pop wrote: > For most architectures this looks OK, except for the following: > - S/390 kernel udebs don't match kernel image on s.d.o > - For mips the r4k and r5k kernel flavors match, but for sb1-swarm-bn > the kernel udebs don't match kernel image on s.d.o

Re: Timeline for r3

2006-06-30 Thread dann frazier
On Fri, Jun 30, 2006 at 03:45:27PM +0100, Steve McIntyre wrote: > On Thu, Jun 29, 2006 at 08:03:32PM +0100, Steve McIntyre wrote: > >On Thu, Jun 29, 2006 at 12:13:08PM -0600, dann frazier wrote: > >>On Thu, Jun 29, 2006 at 06:40:01PM +0200, Frans Pop wrote: > >> > >>> - For mips the r4k and r5k ker

Re: Timeline for r3

2006-06-30 Thread Steve McIntyre
On Thu, Jun 29, 2006 at 08:03:32PM +0100, Steve McIntyre wrote: >On Thu, Jun 29, 2006 at 12:13:08PM -0600, dann frazier wrote: >>On Thu, Jun 29, 2006 at 06:40:01PM +0200, Frans Pop wrote: >> >>> - For mips the r4k and r5k kernel flavors match, but for sb1-swarm-bn the >>> kernel udebs don't match

Re: Timeline for r3

2006-06-30 Thread Steve McIntyre
On Thu, Jun 29, 2006 at 08:03:32PM +0100, Steve McIntyre wrote: >On Thu, Jun 29, 2006 at 12:13:08PM -0600, dann frazier wrote: >>On Thu, Jun 29, 2006 at 06:40:01PM +0200, Frans Pop wrote: >> >>> - For mips the r4k and r5k kernel flavors match, but for sb1-swarm-bn the >>> kernel udebs don't match

Re: Timeline for r3

2006-06-29 Thread Steve McIntyre
On Thu, Jun 29, 2006 at 12:13:08PM -0600, dann frazier wrote: >On Thu, Jun 29, 2006 at 06:40:01PM +0200, Frans Pop wrote: > >> - For mips the r4k and r5k kernel flavors match, but for sb1-swarm-bn the >> kernel udebs don't match kernel image on s.d.o > >hey Steve: would you mind rebuilding this o

Re: Timeline for r3

2006-06-29 Thread dann frazier
On Thu, Jun 29, 2006 at 06:40:01PM +0200, Frans Pop wrote: > For most architectures this looks OK, except for the following: > - AMD64 kernel udebs don't match as AMD64 kernel image not yet on > s.d.o nothing to do till amd64 makes it > - S/390 kernel udebs don't match kernel image on s.d.o I wi

Re: Timeline for r3

2006-06-29 Thread dann frazier
On Thu, Jun 29, 2006 at 06:59:43PM +0200, Frans Pop wrote: > On Thursday 29 June 2006 18:40, Frans Pop wrote: > > - dannf has updated 2.2.25 kernel udebs for m68k, but I can find no > > matching security update for those on s.d.o > > Probably this is not an issue. > I suspect there actually is

Re: Timeline for r3

2006-06-29 Thread Stephen R Marenka
On Thu, Jun 29, 2006 at 06:40:01PM +0200, Frans Pop wrote: > - m68k kernel udebs were originally built incorrectly; I understood this > has been corrected but new udebs are not yet available in gluck:~dannf Should still be at gluck:~smarenka/m68k-lkdi-take2 -- Stephen R. Marenka If life's

Re: Timeline for r3

2006-06-29 Thread Frans Pop
On Thursday 29 June 2006 18:40, Frans Pop wrote: > - dannf has updated 2.2.25 kernel udebs for m68k, but I can find no > matching security update for those on s.d.o Probably this is not an issue. I suspect there actually is no security update for the m68k 2.2.25 kernels. The kernel udebs do ma

Re: Timeline for r3

2006-06-29 Thread Frans Pop
On Friday 23 June 2006 23:07, Martin Zobel-Helas wrote: > We have no fixed "freeze" date for r3 yet, but i currently plan to > freeze one or two weeks after the pending 2.6 kernel update is pushed > by the security team. If this is not enough time for the porters, > please cluebat me. Current stat

Re: Timeline for r3

2006-06-27 Thread Martin Zobel-Helas
Hi security-team, > I currently consider #373854 as RC for r3, and ask the security team to > either update it with another DSA or to tell us if we should fix it via > proposed-updates. I also recently became aware off #374733, #375120, #373581 and #373980 (all package libfreetype6, in connection

Re: Timeline for r3

2006-06-23 Thread Steve Kemp
On Fri, Jun 23, 2006 at 11:07:51PM +0200, Martin Zobel-Helas wrote: > I currently consider #373854 as RC for r3, and ask the security team to > either update it with another DSA or to tell us if we should fix it via > proposed-updates. I think there should be an update for this, Joey if you ag

Timeline for r3

2006-06-23 Thread Martin Zobel-Helas
Hi, to keep everyone in the loop i would like to discuss my current plans for the r3 timeline. We have no fixed "freeze" date for r3 yet, but i currently plan to freeze one or two weeks after the pending 2.6 kernel update is pushed by the security team. If this is not enough time for the porters,