Re: Strongly advise preventing new hotplug from getting into 'sarge' yet

2004-04-06 Thread Steve Langasek
On Wed, Apr 07, 2004 at 12:10:56AM -0400, Nathanael Nerode wrote: > > The normal effect of such a conflict is to impose the restriction "you > > can't upgrade hotplug without removing alsa", which I trust most users > > of testing can cope with reasonably when it scrolls across their screen. > > Wa

Re: Strongly advise preventing new hotplug from getting into 'sarge' yet

2004-04-06 Thread Steve Langasek
On Wed, Apr 07, 2004 at 12:06:11AM -0400, Nathanael Nerode wrote: > > I would note that any bug that can be described as "fake bug to keep foo > > out of testing until bar is ready" is almost certain to cause problems > > with partial upgrades. Although generally discouraged by policy, would > > a

Re: Strongly advise preventing new hotplug from getting into 'sarge' yet

2004-04-06 Thread Nathanael Nerode
Steve Langasek wrote: > On Tue, Apr 06, 2004 at 08:20:54AM -0400, David B Harris wrote: >> On Tue, 6 Apr 2004 01:15:13 -0500 >> Steve Langasek <[EMAIL PROTECTED]> wrote: >> > > Can one of the release managers comment on this? Me and the other >> > > ALSA maintainers had planned on changing (perhap

Re: Strongly advise preventing new hotplug from getting into 'sarge' yet

2004-04-06 Thread Nathanael Nerode
Steve Langasek wrote: > On Thu, Apr 01, 2004 at 10:27:30AM -0500, David B Harris wrote: >> On Wed, 31 Mar 2004 15:12:58 -0500 >> [EMAIL PROTECTED] (Nathanael Nerode) wrote: >> > I filed bug 241225 to prevent new hotplug from going into sarge until >> > the ALSA issue is resolved. > >> Can one of

Re: Strongly advise preventing new hotplug from getting into 'sarge' yet

2004-04-06 Thread Steve Langasek
On Tue, Apr 06, 2004 at 08:20:54AM -0400, David B Harris wrote: > On Tue, 6 Apr 2004 01:15:13 -0500 > Steve Langasek <[EMAIL PROTECTED]> wrote: > > > Can one of the release managers comment on this? Me and the other ALSA > > > maintainers had planned on changing (perhaps getting rid of) the init >

Re: Strongly advise preventing new hotplug from getting into 'sarge' yet

2004-04-06 Thread David B Harris
On Tue, 6 Apr 2004 01:15:13 -0500 Steve Langasek <[EMAIL PROTECTED]> wrote: > > Can one of the release managers comment on this? Me and the other ALSA > > maintainers had planned on changing (perhaps getting rid of) the init > > script for Sarge+1. If we need to accelerate these plans, we wouldn't

Re: Strongly advise preventing new hotplug from getting into 'sarge' yet

2004-04-06 Thread Steve Langasek
On Thu, Apr 01, 2004 at 10:27:30AM -0500, David B Harris wrote: > On Wed, 31 Mar 2004 15:12:58 -0500 > [EMAIL PROTECTED] (Nathanael Nerode) wrote: > > I filed bug 241225 to prevent new hotplug from going into sarge until the > > ALSA issue is resolved. > Can one of the release managers comment on

Re: Strongly advise preventing new hotplug from getting into 'sarge' yet

2004-04-01 Thread David B Harris
On Wed, 31 Mar 2004 15:12:58 -0500 [EMAIL PROTECTED] (Nathanael Nerode) wrote: > I filed bug 241225 to prevent new hotplug from going into sarge until the > ALSA issue is resolved. Can one of the release managers comment on this? Me and the other ALSA maintainers had planned on changing (perhaps g

Re: Strongly advise preventing new hotplug from getting into 'sarge' yet

2004-04-01 Thread Riku Voipio
On Wed, Mar 31, 2004 at 03:12:58PM -0500, Nathanael Nerode wrote: > New hotplug currently breaks alsa for basically everyone using > kernel 2.6. This is a nasty regression, regardless of whose "fault" it is, > and it seems extremely inappropriate to allow this regression to propagate > into sarge.

Strongly advise preventing new hotplug from getting into 'sarge' yet

2004-03-31 Thread Nathanael Nerode
I filed bug 241225 to prevent new hotplug from going into sarge until the ALSA issue is resolved. New hotplug currently breaks alsa for basically everyone using kernel 2.6. This is a nasty regression, regardless of whose "fault" it is, and it seems extremely inappropriate to allow this regression