Re: linux-image-*-dbg for squeeze?

2010-03-06 Thread Lucas Nussbaum
[ Adding ftpmasters to To: ] On 05/03/10 at 19:34 +0100, Bastian Blank wrote: On Fri, Mar 05, 2010 at 09:07:50AM +0100, Lucas Nussbaum wrote: I wonder what we (as Debian) could do about it. Would it make sense to sponsor a very fast machine that the kernel team could use to build the

Re: linux-image-*-dbg for squeeze?

2010-03-05 Thread Lucas Nussbaum
On 04/03/10 at 16:40 -0700, John Wright wrote: Hi kernel team, (Cc-ing -devel to get more eyes on the subject, since I'm soliciting ideas here... See [1] for some context.) What would it take to get kernel debuginfo into squeeze? As I understand it, the main blockers were [2]: Hi John,

Re: linux-image-*-dbg for squeeze?

2010-03-05 Thread John Wright
Hi Lucas, On Fri, Mar 05, 2010 at 09:07:50AM +0100, Lucas Nussbaum wrote: On 04/03/10 at 16:40 -0700, John Wright wrote: Hi kernel team, (Cc-ing -devel to get more eyes on the subject, since I'm soliciting ideas here... See [1] for some context.) What would it take to get kernel

Re: linux-image-*-dbg for squeeze?

2010-03-05 Thread Bastian Blank
On Fri, Mar 05, 2010 at 09:07:50AM +0100, Lucas Nussbaum wrote: I wonder what we (as Debian) could do about it. Would it make sense to sponsor a very fast machine that the kernel team could use to build the kernels and upload from, replacing kernel-archive.buildserver.net ? The easiest fix is

linux-image-*-dbg for squeeze?

2010-03-04 Thread John Wright
Hi kernel team, (Cc-ing -devel to get more eyes on the subject, since I'm soliciting ideas here... See [1] for some context.) What would it take to get kernel debuginfo into squeeze? As I understand it, the main blockers were [2]: 1) It would blow up the archive by ~10 GB - This is a

Re: linux-image-*-dbg for squeeze?

2010-03-04 Thread Andreas Marschke
My 2 cents being that I'm far from part of the kernel team: Am Freitag 05 März 2010 00:40:27 schrieb John Wright: Hi kernel team, What would it take to get kernel debuginfo into squeeze? As I understand it, the main blockers were [2]: 1) It would blow up the archive by ~10 GB -