Re: Bug#219582: ITP: linux -- Linux 2.4 kernel
Robert Millan <firstname.lastname@example.org> wrote:
> On Mon, Nov 10, 2003 at 09:29:58AM -0500, Michael Poole wrote:
>> 5) How will you handle architectures where the current upstream kernel
>> is not based on the same version as your package? The main suggestion
>> I see is that they'd have to use the current system for their kernels,
>> which seems very bad for consistency.
> I pretend to package all upstream branches (2.4, 2.6, etc). The -defaults
> package can be selective across arquitectures (like gcc-defaults does).
The question was: How do you provide 2.4.x for architecture
blah and 2.4.y for architecture foo, which are two versions of the
same "upstream branch".
Afaict you were proposing to have one package for each upstream
/branch/. You cannot have linux-2.4_2.4.x.orig.tar.gz and
linux-2.4_2.4.y.orig.tar.gz at the same time in the Debian archive,
once you upload 2.4.y to sid, 2.4.x with x<<y is not available in sid
Hey, da ist ein Ballonautomat auf der Toilette!
Unofficial _Debian-packages_ of latest unstable _tin_