[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#219582: ITP: linux -- Linux 2.4 kernel

On Saturday 08 November 2003 00:20, viro@parcelfarce.linux.theplanet.co.uk 
> On Fri, Nov 07, 2003 at 04:22:27PM -0500, Daniel Jacobowitz wrote:
> > Then how do you suggest maintaining a kernel 2.4.20 for one
> > architecture and a 2.4.22 for another architecture, when you can't even
> > test on either of them?  And how do you expect to ever upgrade the
> > result without duplicating all the work done by all the existing kernel
> > package maintainers for all Debian architectures?
> >
> > This doesn't even make any sense.  Might as well just set Architecture:
> > i386.
> Situation when 2.4.22 does not work on architecture in question is a *bug*,
> plain and simple.  Same as when 2.3.2 doesn't work on the same
> architecture. And correct way to deal with that is to report these bugs
> upstream and/or submit patches fixing them.

I guess something like a 'debian kernel policy' doc is needed here... like 
debian's perl-policy or java-policy ? There must be an common approved 
procedure to deal with these tasks.
*If Debian needs some arch-specific kernel changes (or any other kernel 
functionality), not present in vanillas then try to push them upstream (lkml) 
* If the above failed, try to realize why the upstream kernel developers 
reject these changes. If it is because of a bad design and/or coding then 
review them again and ask for help if necessary, if upstream drops these 
changes again for no good reason but they are needed to save your arches, 
* start a discussion on debian-kernels (dkml? it is not just for packaging 
linux kernel packages, but bsd and hurd-on-gnumach or whatever it works on 
this week) of how to add these changes, e.g. as separate kernel patch 
packages or included by default in debian kernel source package. This must be 
discussed to achieve one kernel source package suitable for all hardware 

I think debian kernel team should host its packaging stuff (the debian/ dir) 
on cvs.debian.org or at any subversion site. Kernel packages must be 
processed just like glibc packages get, except that there are more than one 
kernel in debian (e.g. linux, bsd, hurd-on-gnumach). And please, relevant 
names are needed, e.g. linux-source, linux-image, etc... 

pub  4096R/0E4BD0AB 2003-03-18 <keyserver.bu.edu>
1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB 

Reply to: