Re: Decision about oot-modules for etch

2006-08-07 Thread Steve Langasek
On Wed, Aug 02, 2006 at 05:52:34PM +0200, Daniel Baumann wrote: > Daniel Baumann wrote: > > Can you make an announcement to all oot-module maintainers, telling them > > that they should put their packages together into linux-modules-extra > > (for main) or a similar one for contrib, and if they're

Re: Decision about oot-modules for etch

2006-08-04 Thread Marc 'HE' Brockschmidt
Daniel Baumann <[EMAIL PROTECTED]> writes: > Atm, there are the following questions open: > > * What is the ETA for the linux-modules-extra package in the archive? That is something the kernel team needs to plan, the release team has no schedule for it. It's not an explicit release target or goa

Re: Decision about oot-modules for etch

2006-08-03 Thread Sven Luther
On Mon, Jul 31, 2006 at 12:46:09PM +0200, Daniel Baumann wrote: > Hi, > > as stated in [0], waldi is working on an oot-module conglomeration > package to solve NEW spamming for oot-module packages when the kernel > ABI is bumped. My take is that there should be no step taken to solve the NEW spam

Re: Decision about oot-modules for etch

2006-08-02 Thread Daniel Baumann
Daniel Baumann wrote: > Can you make an announcement to all oot-module maintainers, telling them > that they should put their packages together into linux-modules-extra > (for main) or a similar one for contrib, and if they're not doing it, > they will end up in an unsupported (no updates for point

Re: Decision about oot-modules for etch

2006-08-01 Thread Bastian Blank
On Tue, Aug 01, 2006 at 02:05:24AM +0200, Marco d'Itri wrote: > In linux.debian.kernel Bastian Blank <[EMAIL PROTECTED]> wrote: > >> [2] The ipw drivers are in the kernel mainline (ipw3945 will hopefully > >> follow soon). > >Only if they remove the dependency on the binary-only deamon. I'm > >

Re: Decision about oot-modules for etch

2006-07-31 Thread Marco d'Itri
In linux.debian.kernel Bastian Blank <[EMAIL PROTECTED]> wrote: >> [2] The ipw drivers are in the kernel mainline (ipw3945 will hopefully >> follow soon). >Only if they remove the dependency on the binary-only deamon. I'm >currently doing this for my own anyway. Matthew Garrett has an almost w

Re: Decision about oot-modules for etch

2006-07-31 Thread Daniel Baumann
Steve Langasek wrote: > I don't see anything of the sort stated there, and it's not the kernel > team's place to disallow such packages anyway. I asked waldi for explaining this 'unsupported idea' which svenl was indicating in the mentioned mail. waldi explained me in that IRC discussion at the en

Re: Decision about oot-modules for etch

2006-07-31 Thread Steve Langasek
On Mon, Jul 31, 2006 at 12:46:09PM +0200, Daniel Baumann wrote: > As stated in [1], there are though about to not allow other oot-modules > in main outside of the conglomeration package for etch. > [1] http://lists.debian.org/debian-kernel/2006/06/msg00441.html I don't see anything of the sort s

Re: Decision about oot-modules for etch

2006-07-31 Thread Otavio Salvador
Daniel Baumann <[EMAIL PROTECTED]> writes: > Can you make an announcement to all oot-module maintainers, telling them > that they should put their packages together into linux-modules-extra > (for main) or a similar one for contrib, and if they're not doing it, > they will end up in an unsupported

Re: Decision about oot-modules for etch

2006-07-31 Thread Daniel Baumann
Andreas Barth wrote: > I don't see any release-team decisions required right now. :) I beg to differ, see below. > Basically, I tend to something like: > >> * Will be oot-modules in main outside of the linux-modules-extra be >> removed by the release-team for etch? > > If there are fewer

Re: Decision about oot-modules for etch

2006-07-31 Thread Andreas Barth
* Daniel Baumann ([EMAIL PROTECTED]) [060731 12:46]: > Now, I would like to have a definitive statement for that to get > everything prepared for etch (basically the ipw packages[2]). This > means, a decision of the kernel-team and the release-team is required. I don't see any release-team decisio

Re: Decision about oot-modules for etch

2006-07-31 Thread Andreas Barth
* Daniel Baumann ([EMAIL PROTECTED]) [060731 16:29]: > Andreas Barth wrote: > > AFAICS ipw doesn't provide oot-modules, but only ipw*-source. Is that > > correct? > As I wrot in '[2]' of the previous mail, I want ipw2100 and ipw2200 > (and, therefore also ieee8201) as oot, *although* they are alre

Re: Decision about oot-modules for etch

2006-07-31 Thread Daniel Baumann
Andreas Barth wrote: > AFAICS ipw doesn't provide oot-modules, but only ipw*-source. Is that > correct? As I wrot in '[2]' of the previous mail, I want ipw2100 and ipw2200 (and, therefore also ieee8201) as oot, *although* they are already in mainline. But I'm not going to do that when a few weeks

Re: Decision about oot-modules for etch

2006-07-31 Thread Andreas Barth
* Daniel Baumann ([EMAIL PROTECTED]) [060731 12:46]: > as stated in [0], waldi is working on an oot-module conglomeration > package to solve NEW spamming for oot-module packages when the kernel > ABI is bumped. > Now, I would like to have a definitive statement for that to get > everything prepare

Re: Decision about oot-modules for etch

2006-07-31 Thread Bastian Blank
On Mon, Jul 31, 2006 at 12:46:09PM +0200, Daniel Baumann wrote: > * What is the ETA for the linux-modules-extra package in the archive? I'm just finished with my exams, so I hope I can get it finished this week. > * Will there be something similar for contrib modules too (e.g. > linux-mod

Decision about oot-modules for etch

2006-07-31 Thread Daniel Baumann
Hi, as stated in [0], waldi is working on an oot-module conglomeration package to solve NEW spamming for oot-module packages when the kernel ABI is bumped. As stated in [1], there are though about to not allow other oot-modules in main outside of the conglomeration package for etch. As discussed