On Fri, May 26, 2006 at 11:39:30AM +0200, Andreas Barth wrote:
> * Sven Luther ([EMAIL PROTECTED]) [060526 10:20]:
> > Well, it was my understanding that both those packages where living in a
> > differnt section, namely etch and etch-, which would take care of
> > the problem. Failing that, it is
On Thu, May 25, 2006 at 05:10:57PM -0700, Steve Langasek wrote:
> On Tue, May 23, 2006 at 07:08:41PM +0200, Sven Luther wrote:
> > On Tue, May 23, 2006 at 09:47:08AM -0700, Steve Langasek wrote:
> > > On Mon, May 22, 2006 at 11:38:46PM +0200, Sven Luther wrote:
> > > > On Mon, May 22, 2006 at 01:52
* Sven Luther ([EMAIL PROTECTED]) [060526 10:20]:
> Well, it was my understanding that both those packages where living in a
> differnt section, namely etch and etch-, which would take care of
> the problem. Failing that, it is easy enough to handle the problem in the same
> way as we want to handl
On Tue, May 23, 2006 at 07:08:41PM +0200, Sven Luther wrote:
> On Tue, May 23, 2006 at 09:47:08AM -0700, Steve Langasek wrote:
> > On Mon, May 22, 2006 at 11:38:46PM +0200, Sven Luther wrote:
> > > On Mon, May 22, 2006 at 01:52:47PM -0700, Steve Langasek wrote:
> > > > > Perhaps we disable new kern
* Sven Luther ([EMAIL PROTECTED]) [060524 12:14]:
> On Wed, May 24, 2006 at 12:04:59PM +0200, Andreas Barth wrote:
> > There will definitly be a time when it is too late to replace the kernel
> > without delaying the release (just consider that we e.g. notice after
> > starting the CD build that th
On Wed, May 24, 2006 at 12:04:59PM +0200, Andreas Barth wrote:
> * Sven Luther ([EMAIL PROTECTED]) [060524 11:52]:
> > On Wed, May 24, 2006 at 11:35:00AM +0200, Andreas Barth wrote:
> > > * Sven Luther ([EMAIL PROTECTED]) [060524 11:23]:
> > > > On Wed, May 24, 2006 at 10:31:08AM +0200, Andreas Bar
* Sven Luther ([EMAIL PROTECTED]) [060524 11:52]:
> On Wed, May 24, 2006 at 11:35:00AM +0200, Andreas Barth wrote:
> > * Sven Luther ([EMAIL PROTECTED]) [060524 11:23]:
> > > On Wed, May 24, 2006 at 10:31:08AM +0200, Andreas Barth wrote:
> > > > You are ignoring that we have scheduled a time to upd
On Wed, May 24, 2006 at 11:35:00AM +0200, Andreas Barth wrote:
> * Sven Luther ([EMAIL PROTECTED]) [060524 11:23]:
> > On Wed, May 24, 2006 at 10:31:08AM +0200, Andreas Barth wrote:
> > > You are ignoring that we have scheduled a time to update the kernel
> > > again before release of etch.
> >
>
* Sven Luther ([EMAIL PROTECTED]) [060524 11:23]:
> On Wed, May 24, 2006 at 10:31:08AM +0200, Andreas Barth wrote:
> > You are ignoring that we have scheduled a time to update the kernel
> > again before release of etch.
>
> Ah, nice. But would this include an abi-changing kernel upgrade ? I fear
On Wed, May 24, 2006 at 10:31:08AM +0200, Andreas Barth wrote:
> * Sven Luther ([EMAIL PROTECTED]) [060524 06:33]:
> > Well, as a proof of my claims, the sarge d-i released with a known remote
> > security hole, and there has been no (or maybe 1 by now ?) d-i update since
> > then.
>
> You mean, a
On Wed, May 24, 2006 at 10:27:14AM +0200, Andreas Barth wrote:
> * dann frazier ([EMAIL PROTECTED]) [060524 05:33]:
> > On Sun, May 21, 2006 at 10:46:44PM +0200, Sven Luther wrote:
> > > On Sun, May 21, 2006 at 01:09:45PM -0500, dann frazier wrote:
> > > > Kernel udeb creation process (possibly usi
* Sven Luther ([EMAIL PROTECTED]) [060524 06:33]:
> Well, as a proof of my claims, the sarge d-i released with a known remote
> security hole, and there has been no (or maybe 1 by now ?) d-i update since
> then.
You mean, a remote root exploitable hole? If so, which bug, and why
wasn't that inform
* dann frazier ([EMAIL PROTECTED]) [060524 05:33]:
> On Sun, May 21, 2006 at 10:46:44PM +0200, Sven Luther wrote:
> > On Sun, May 21, 2006 at 01:09:45PM -0500, dann frazier wrote:
> > > Kernel udeb creation process (possibly using k-p?)
> > > -
> > >
On Tue, May 23, 2006 at 10:16:37PM -0500, dann frazier wrote:
> On Sun, May 21, 2006 at 10:46:44PM +0200, Sven Luther wrote:
> > On Sun, May 21, 2006 at 01:09:45PM -0500, dann frazier wrote:
> > > Kernel udeb creation process (possibly using k-p?)
> > > -
On Sun, May 21, 2006 at 10:46:44PM +0200, Sven Luther wrote:
> On Sun, May 21, 2006 at 01:09:45PM -0500, dann frazier wrote:
> > Kernel udeb creation process (possibly using k-p?)
> > -
> > If we build all of the *existing* udebs from a single source,
On Mon, May 22, 2006 at 11:38:46PM +0200, Sven Luther wrote:
> On Mon, May 22, 2006 at 01:52:47PM -0700, Steve Langasek wrote:
> > > Perhaps we disable new kernel features for etch 1/2? e.g., limit new
> > > feature to new hardware support. For example, we wouldn't want to
> > > turn on something
On Tue, May 23, 2006 at 09:47:08AM -0700, Steve Langasek wrote:
> On Mon, May 22, 2006 at 11:38:46PM +0200, Sven Luther wrote:
> > On Mon, May 22, 2006 at 01:52:47PM -0700, Steve Langasek wrote:
> > > > Perhaps we disable new kernel features for etch 1/2? e.g., limit new
> > > > feature to new har
On Tue, May 23, 2006 at 09:10:54AM +0200, Geert Stappers wrote:
>
> [ keeping the cross-post and please keep it cross-posted ]
>
> On Sun, May 21, 2006 at 01:09:45PM -0500, dann frazier wrote:
> > hey,
> > Frans Pop assembled an informal BoF at DebConf to discuss cross-team
> > issues related
[ keeping the cross-post and please keep it cross-posted ]
On Sun, May 21, 2006 at 01:09:45PM -0500, dann frazier wrote:
> hey,
> Frans Pop assembled an informal BoF at DebConf to discuss cross-team
> issues related to the kernel[1].
>
> We discussed the following topics:
> * Non-free modu
On Mon, May 22, 2006 at 01:52:47PM -0700, Steve Langasek wrote:
> > Perhaps we disable new kernel features for etch 1/2? e.g., limit new
> > feature to new hardware support. For example, we wouldn't want to
> > turn on something as drastic as preempt in a stable update.
>
> So how do you structu
On Sun, May 21, 2006 at 01:09:45PM -0500, dann frazier wrote:
> hey,
> Frans Pop assembled an informal BoF at DebConf to discuss cross-team
> issues related to the kernel[1]. Attendees included:
Sorry I wasn't able to make this meeting, guys.
Random thoughts:
> Kernel Updates During Etch Life
On Sun, May 21, 2006 at 10:10:51PM +0200, Bastian Blank wrote:
> > Frans believes that sepearate source packages are more feasible for allowing
> > this type of shuffling
>
> If someone goes crazy, it may see this as GPL violation.
Ah, excellent point. The source producing some of the .udeb kerne
On Sun, May 21, 2006 at 01:09:45PM -0500, dann frazier wrote:
> Kernel udeb creation process (possibly using k-p?)
> -
> If we build all of the *existing* udebs from a single source, we outgrow
> the limit of the Binary: field in the control file.
Hu
[ drop debian-release from CC ]
On Sun, May 21, 2006 at 01:09:45PM -0500, dann frazier wrote:
> Kernel udeb creation process (possibly using k-p?)
> -
> If we build all of the *existing* udebs from a single source, we outgrow
> the limit of the Binar
hey,
Frans Pop assembled an informal BoF at DebConf to discuss cross-team
issues related to the kernel[1]. Attendees included:
Micah Anderson (micah)
Andreas Barth (aba)
dann frazier (dannf)
Joey Hess (joeyh)
Moritz Muehlenhoff (jmm)
Frans Pop (fjp)
Manoj Srivastava (manoj)
...a
25 matches
Mail list logo
