Re: 6.0.7 planning

2013-02-20 Thread Ben Hutchings
On Wed, 2013-02-20 at 07:17 +, Adam D. Barratt wrote: > On Sun, 2013-02-17 at 15:36 -0800, dann frazier wrote: > > Agreed; and I think I was unclear. I was taking for granted that we > > *will* do a 46squeeze2 now w/ the CVE-2013-0871 fix and bypass > > 46squeeze1. 46squeeze2 would provide the

Re: 6.0.7 planning

2013-02-19 Thread Adam D. Barratt
On Sun, 2013-02-17 at 15:36 -0800, dann frazier wrote: > Agreed; and I think I was unclear. I was taking for granted that we > *will* do a 46squeeze2 now w/ the CVE-2013-0871 fix and bypass > 46squeeze1. 46squeeze2 would provide the security-only option. > > The question was whether or not we shou

Re: 6.0.7 planning

2013-02-17 Thread Ben Hutchings
On Sun, 2013-02-17 at 22:42 +, Adam D. Barratt wrote: > On Sun, 2013-02-17 at 13:33 -0800, dann frazier wrote: > > On Sun, Feb 17, 2013 at 03:14:04PM +, Adam D. Barratt wrote: > > > I gather there's a chance there might need to be further security > > > updates; will that mean we need anoth

Re: 6.0.7 planning

2013-02-17 Thread dann frazier
On Sun, Feb 17, 2013 at 11:12:18PM +, Ben Hutchings wrote: > On Sun, 2013-02-17 at 13:33 -0800, dann frazier wrote: > > On Sun, Feb 17, 2013 at 03:14:04PM +, Adam D. Barratt wrote: > > > On Fri, 2013-02-15 at 11:32 +, Adam D. Barratt wrote: > > > > On Fri, 2013-02-15 at 01:41 +, Ben

Re: 6.0.7 planning

2013-02-17 Thread Ben Hutchings
On Sun, 2013-02-17 at 13:33 -0800, dann frazier wrote: > On Sun, Feb 17, 2013 at 03:14:04PM +, Adam D. Barratt wrote: > > On Fri, 2013-02-15 at 11:32 +, Adam D. Barratt wrote: > > > On Fri, 2013-02-15 at 01:41 +, Ben Hutchings wrote: > > > > On Thu, 2013-02-14 at 10:28 -0800, dann frazi

Re: 6.0.7 planning

2013-02-17 Thread Adam D. Barratt
On Sun, 2013-02-17 at 13:33 -0800, dann frazier wrote: > On Sun, Feb 17, 2013 at 03:14:04PM +, Adam D. Barratt wrote: > > I gather there's a chance there might need to be further security > > updates; will that mean we need another update in p-u? > > Possibly; an alternative would be to releas

Re: 6.0.7 planning

2013-02-17 Thread dann frazier
On Sun, Feb 17, 2013 at 03:14:04PM +, Adam D. Barratt wrote: > On Fri, 2013-02-15 at 11:32 +, Adam D. Barratt wrote: > > On Fri, 2013-02-15 at 01:41 +, Ben Hutchings wrote: > > > On Thu, 2013-02-14 at 10:28 -0800, dann frazier wrote: > > > > Security update has been uploaded. I'll post

Re: 6.0.7 planning

2013-02-17 Thread Adam D. Barratt
On Fri, 2013-02-15 at 11:32 +, Adam D. Barratt wrote: > On Fri, 2013-02-15 at 01:41 +, Ben Hutchings wrote: > > On Thu, 2013-02-14 at 10:28 -0800, dann frazier wrote: > > > Security update has been uploaded. I'll post the builds somewhere as > > > they become available for anyone interested

Re: ia32-libs-* updates (was: Re: 6.0.7 planning)

2013-02-16 Thread Adam D. Barratt
On Sat, 2013-02-16 at 13:15 +0100, Thijs Kinkhorst wrote: > Op vrijdag 15 februari 2013 17:58:23 schreef Adam D. Barratt: > > On Mon, 2013-02-11 at 10:41 +0100, Thijs Kinkhorst wrote: > > > [ cups (1.4.4-7+squeeze2) stable-security; urgency=high ] > > > > Our sanity check grumbled about this on

Re: ia32-libs-* updates (was: Re: 6.0.7 planning)

2013-02-16 Thread Thijs Kinkhorst
Op vrijdag 15 februari 2013 17:58:23 schreef Adam D. Barratt: > On Mon, 2013-02-11 at 10:41 +0100, Thijs Kinkhorst wrote: > > [ cups (1.4.4-7+squeeze2) stable-security; urgency=high ] > > Our sanity check grumbled about this one, as p-u has +squeeze3; is that > intentional? I can't remember wha

ia32-libs-* updates (was: Re: 6.0.7 planning)

2013-02-15 Thread Adam D. Barratt
On Mon, 2013-02-11 at 10:41 +0100, Thijs Kinkhorst wrote: > [ cups (1.4.4-7+squeeze2) stable-security; urgency=high ] Our sanity check grumbled about this one, as p-u has +squeeze3; is that intentional? I can't remember what we've done in such situations previously. Regards, Adam -- To UNS

Re: 6.0.7 planning

2013-02-15 Thread Adam D. Barratt
On Fri, 2013-02-15 at 01:41 +, Ben Hutchings wrote: > On Thu, 2013-02-14 at 10:28 -0800, dann frazier wrote: > > Security update has been uploaded. I'll post the builds somewhere as > > they become available for anyone interested in testing. > > Version 2.6.32-48 has also been uploaded. Flagg

Re: 6.0.7 planning

2013-02-14 Thread Ben Hutchings
On Thu, 2013-02-14 at 10:28 -0800, dann frazier wrote: > On Wed, Feb 13, 2013 at 03:34:51PM +, Ben Hutchings wrote: > > On Wed, 2013-02-13 at 15:18 +, Adam D. Barratt wrote: > > > On 12.02.2013 02:15, Ben Hutchings wrote: > > > > One or other of us will then need to merge the squeeze-securi

Re: 6.0.7 planning

2013-02-14 Thread dann frazier
On Wed, Feb 13, 2013 at 03:34:51PM +, Ben Hutchings wrote: > On Wed, 2013-02-13 at 15:18 +, Adam D. Barratt wrote: > > On 12.02.2013 02:15, Ben Hutchings wrote: > > > One or other of us will then need to merge the squeeze-security > > > branch > > > into squeeze and upload -48 in time for

Re: 6.0.7 planning

2013-02-13 Thread dann frazier
On Wed, Feb 13, 2013 at 03:34:51PM +, Ben Hutchings wrote: > On Wed, 2013-02-13 at 15:18 +, Adam D. Barratt wrote: > > On 12.02.2013 02:15, Ben Hutchings wrote: > > > One or other of us will then need to merge the squeeze-security > > > branch > > > into squeeze and upload -48 in time for

Re: 6.0.7 planning

2013-02-13 Thread Ben Hutchings
On Wed, 2013-02-13 at 15:18 +, Adam D. Barratt wrote: > On 12.02.2013 02:15, Ben Hutchings wrote: > > One or other of us will then need to merge the squeeze-security > > branch > > into squeeze and upload -48 in time for the point release. > > Is there an ETA for that? Sorry for chasing, but

Re: 6.0.7 planning

2013-02-13 Thread Adam D. Barratt
On 12.02.2013 02:15, Ben Hutchings wrote: One or other of us will then need to merge the squeeze-security branch into squeeze and upload -48 in time for the point release. Is there an ETA for that? Sorry for chasing, but if we're going to go for the 23rd (which is looking likely atm) we'd be

Re: 6.0.7 planning

2013-02-12 Thread Adam D. Barratt
On 12.02.2013 13:08, Philipp Kern wrote: On Sun, Feb 10, 2013 at 04:25:38PM +, Adam D. Barratt wrote: We're somewhat overdue with the next Squeeze point release (6.0.7) and it'd be good to get it done before the wheezy release, so that we can pull in some upgrade fixes. As an opening gambit

Re: 6.0.7 planning

2013-02-12 Thread Philipp Kern
Hi, sorry for the delay. On Sun, Feb 10, 2013 at 04:25:38PM +, Adam D. Barratt wrote: > We're somewhat overdue with the next Squeeze point release (6.0.7) and > it'd be good to get it done before the wheezy release, so that we can > pull in some upgrade fixes. As an opening gambit, some propo

Re: 6.0.7 planning

2013-02-11 Thread Ben Hutchings
On Mon, 2013-02-11 at 08:36 -0800, dann frazier wrote: > On Mon, Feb 11, 2013 at 03:41:03AM +, Ben Hutchings wrote: > > On Sun, 2013-02-10 at 16:25 +, Adam D. Barratt wrote: > > > Hi, > > > > > > We're somewhat overdue with the next Squeeze point release (6.0.7) and > > > it'd be good to g

Re: 6.0.7 planning

2013-02-11 Thread Joerg Jaspert
On 13118 March 1977, Adam D. Barratt wrote: > We're somewhat overdue with the next Squeeze point release (6.0.7) and > it'd be good to get it done before the wheezy release, so that we can > pull in some upgrade fixes. As an opening gambit, some proposed dates, > all of which appear to currently w

Re: 6.0.7 planning

2013-02-11 Thread dann frazier
On Mon, Feb 11, 2013 at 03:41:03AM +, Ben Hutchings wrote: > On Sun, 2013-02-10 at 16:25 +, Adam D. Barratt wrote: > > Hi, > > > > We're somewhat overdue with the next Squeeze point release (6.0.7) and > > it'd be good to get it done before the wheezy release, so that we can > > pull in so

Re: 6.0.7 planning

2013-02-11 Thread Niels Thykier
On 2013-02-11 10:40, Thijs Kinkhorst wrote: > On Sun, February 10, 2013 17:25, Adam D. Barratt wrote: >> We're somewhat overdue with the next Squeeze point release (6.0.7) and >> it'd be good to get it done before the wheezy release, so that we can >> pull in some upgrade fixes. > > Attached are t

Re: 6.0.7 planning

2013-02-11 Thread Thijs Kinkhorst
On Mon, February 11, 2013 10:40, Thijs Kinkhorst wrote: > On Sun, February 10, 2013 17:25, Adam D. Barratt wrote: >> We're somewhat overdue with the next Squeeze point release (6.0.7) and >> it'd be good to get it done before the wheezy release, so that we can >> pull in some upgrade fixes. > > Att

Re: 6.0.7 planning

2013-02-11 Thread Thijs Kinkhorst
On Sun, February 10, 2013 17:25, Adam D. Barratt wrote: > We're somewhat overdue with the next Squeeze point release (6.0.7) and > it'd be good to get it done before the wheezy release, so that we can > pull in some upgrade fixes. Attached are the proposed updates to ia32-libs and ia32-libs-core a

Re: 6.0.7 planning

2013-02-10 Thread Ben Hutchings
On Sun, 2013-02-10 at 16:25 +, Adam D. Barratt wrote: > Hi, > > We're somewhat overdue with the next Squeeze point release (6.0.7) and > it'd be good to get it done before the wheezy release, so that we can > pull in some upgrade fixes. As an opening gambit, some proposed dates, > all of which

Re: 6.0.7 planning

2013-02-10 Thread Steve McIntyre
On Sun, Feb 10, 2013 at 04:25:38PM +, Adam Barratt wrote: >Hi, > >We're somewhat overdue with the next Squeeze point release (6.0.7) and >it'd be good to get it done before the wheezy release, so that we can >pull in some upgrade fixes. As an opening gambit, some proposed dates, >all of which a

Re: 6.0.7 planning

2013-02-10 Thread Daniel Baumann
all of them fine by me. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a

Re: 6.0.7 planning

2013-02-10 Thread Francesca Ciceri
Hi, On Sun, Feb 10, 2013 at 04:25:38PM +, Adam D. Barratt wrote: > Hi, > > We're somewhat overdue with the next Squeeze point release (6.0.7) and > it'd be good to get it done before the wheezy release, so that we can > pull in some upgrade fixes. As an opening gambit, some proposed dates, >

6.0.7 planning

2013-02-10 Thread Adam D. Barratt
Hi, We're somewhat overdue with the next Squeeze point release (6.0.7) and it'd be good to get it done before the wheezy release, so that we can pull in some upgrade fixes. As an opening gambit, some proposed dates, all of which appear to currently work for me: February 23rd March 2nd March 9th