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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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,
>
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
21 matches
Mail list logo
