Re: Squeeze point release (6.0.5)

2012-05-04 Thread dann frazier
On Thu, May 03, 2012 at 11:14:38PM +0100, Adam D. Barratt wrote: On Mon, 2012-04-30 at 10:09 -0600, dann frazier wrote: On Mon, Apr 30, 2012 at 04:15:31AM +0100, Ben Hutchings wrote: On Sun, 2012-04-29 at 16:36 +0100, Adam D. Barratt wrote: Is the new version ready for upload? It's

Re: Squeeze point release (6.0.5)

2012-05-03 Thread Adam D. Barratt
On Mon, 2012-04-30 at 10:09 -0600, dann frazier wrote: On Mon, Apr 30, 2012 at 04:15:31AM +0100, Ben Hutchings wrote: On Sun, 2012-04-29 at 16:36 +0100, Adam D. Barratt wrote: Is the new version ready for upload? It's looking like the point release will be the 12/13th, so it would be

Re: Squeeze point release (6.0.5)

2012-04-30 Thread dann frazier
On Mon, Apr 30, 2012 at 04:15:31AM +0100, Ben Hutchings wrote: On Sun, 2012-04-29 at 16:36 +0100, Adam D. Barratt wrote: On Thu, 2012-04-26 at 05:00 +0100, Ben Hutchings wrote: I think we're going to need to do another kernel upload before the point release to revert a fix that is worse

Re: Squeeze point release (6.0.5)

2012-04-29 Thread Adam D. Barratt
On Thu, 2012-04-26 at 05:00 +0100, Ben Hutchings wrote: I think we're going to need to do another kernel upload before the point release to revert a fix that is worse than the original bug: Subject: Revert autofs: work around unhappy compat problem on x86-64 This reverts commit

Re: Squeeze point release (6.0.5)

2012-04-29 Thread Adam D. Barratt
On Tue, 2012-04-24 at 21:06 +0100, Adam D. Barratt wrote: 6.0.5 is somewhat overdue now and I've been procrastinating over organising it for a while. So before I find something else to distract myself with, some suggested dates: It looks like the discussion has converged towards: May 12/13:

Re: Squeeze point release (6.0.5)

2012-04-29 Thread Ben Hutchings
On Sun, 2012-04-29 at 16:36 +0100, Adam D. Barratt wrote: On Thu, 2012-04-26 at 05:00 +0100, Ben Hutchings wrote: I think we're going to need to do another kernel upload before the point release to revert a fix that is worse than the original bug: Subject: Revert autofs: work around

Re: Squeeze point release (6.0.5)

2012-04-26 Thread Mark Hymers
On Wed, 25, Apr, 2012 at 09:32:51PM +0100, Steve McIntyre spoke thus.. That will help, but then the issue is more a problem with downloading the images. I've got a full mirror at home, which helps immensely with jigdo downloads. I can try and arrange to have a full local mirror at the BSP

Re: Squeeze point release (6.0.5)

2012-04-26 Thread Steve McIntyre
On Thu, Apr 26, 2012 at 12:22:18PM +0100, Mark Hymers wrote: On Wed, 25, Apr, 2012 at 09:32:51PM +0100, Steve McIntyre spoke thus.. That will help, but then the issue is more a problem with downloading the images. I've got a full mirror at home, which helps immensely with jigdo downloads. I

Re: Squeeze point release (6.0.5)

2012-04-25 Thread Steve McIntyre
On Wed, Apr 25, 2012 at 09:25:17PM +0100, Jonathan Wiltshire wrote: On Tue, Apr 24, 2012 at 09:22:12PM +0100, Steve McIntyre wrote: On Tue, Apr 24, 2012 at 09:06:01PM +0100, Adam Barratt wrote: May 12/13: York BSP. Probably not the best time for CDs, given that Steve would be at the wrong end

Re: Squeeze point release (6.0.5)

2012-04-25 Thread Jonathan Wiltshire
On Tue, Apr 24, 2012 at 09:22:12PM +0100, Steve McIntyre wrote: On Tue, Apr 24, 2012 at 09:06:01PM +0100, Adam Barratt wrote: May 12/13: York BSP. Probably not the best time for CDs, given that Steve would be at the wrong end of the country. (As will I, but that's less of an issue) Not a

Re: Squeeze point release (6.0.5)

2012-04-25 Thread Ben Hutchings
I think we're going to need to do another kernel upload before the point release to revert a fix that is worse than the original bug: Subject: Revert autofs: work around unhappy compat problem on x86-64 This reverts commit 82e43e2a64739caf323ac98641e1250c3808c300 (commit

Re: Squeeze point release (6.0.5)

2012-04-24 Thread Steve McIntyre
On Tue, Apr 24, 2012 at 09:06:01PM +0100, Adam Barratt wrote: Hi, 6.0.5 is somewhat overdue now and I've been procrastinating over organising it for a while. So before I find something else to distract myself with, some suggested dates: May 5/6: Probably doable; would mean we need to close