Re: Scheduling 2.6.17-1

[Sven Luther <sven.luther@wanadoo.fr>]

On Sun, Jun 18, 2006 at 11:58:26PM +0200, Frederik Schueler wrote:
> Hi,
> 
> On Sun, Jun 18, 2006 at 11:47:49PM +0200, Sven Luther wrote:
> > What about :
> > 
> >   We upload linux-2.6 2.6.17 ASAP, and if 2.6.16 is finally the way to go, we
> >   upload linux-2.6.16 or linux-2.6.etch, and propagate this one to testing.
> 
> The problem is: we need a kernel >> 2.6.15 in testing ASAP (2.6.15 is
> really old, and d-i needs a new kernel for the next release candidate).
> 
> 2.6.17 is likely to need 3-4 weeks before it can be considered as a 
> testing candidate. 2.6.16 should already be in testing, but it did not 
> migrate due to various reasons. Thus, we should just try and have a good
> version of it added to testing, without the pressure to beating 2.6.17 into 
> shape within a week.

BTW, do we already have code to chose the gcc version ? I rebuilt 2.6.16-5
yesterday, with gcc 4.1, and it is apparently not ok to use it with the .udeb
already in testing or something, or at least i keep getting strange md5sum
errors on .udeb downloads on a p505 box.

Bastian, can you help me tomorrow afternoon/evening in trying to do a :

  http://people.debian.org/~luther/debian-installer-64bit-2 

install inside a virtual partiton on the augsbourg box ?

Friendly,

Sven Luther