Re: Kernel Security Updates for Sarge

[Horms <horms@verge.net.au>]

On Thu, May 12, 2005 at 11:27:33AM +0200, Thiemo Seufer wrote:
> Horms wrote:
> > On Thu, May 12, 2005 at 10:07:06AM +0200, Thiemo Seufer wrote:
> > > Horms wrote:
> > > [snip]
> > > > For reference, these are the architectues that I believe
> > > > the kernel team handles, and the version of the kernel source
> > > > they are using in Sarge:
> > > > 
> > > >                 Base kernel source version of package in Sarge
> > > > 2.4.27: alpha      kernel-tree-2.4.27-9   (seems to be out of date in SVN)
> > > >         hppa       kernel-tree-2.4.27-8
> > > >         i386       kernel-tree-2.4.27-8
> > > >         ia64       kernel-tree-2.4.27-8
> > > >         mips       kernel-tree-2.4.27-8   (versioned dependancy needs to be
> > > >                                            changed to kernel-tree-2.4.27-8)
> > > 
> > > mips/mipsel uses the kernel-source package as build dependency
> > > instead of kernel-tree.
> > 
> > Ok, but does it patch to a known version before building.
> > That is, if I have kernel-source-2.4.27 2.4.27-8 installed
> > and build the mips kernel image packages, and then I have
> > kernel-source-2.4.27 2.4.27-9 installed, will I get the same result?
> 
> No, it will build against 2.4.27-9. If building against a known
> broken kernel source is preferred for some reason, the build
> dependency could be tightened to match only the 2.4.27-8 source.

Some people beleive that it is a requirement of the GPL
that you should be able to reproduce your binary package.
And as far as I understand for that reason, such a build dependancy
is required for debian packages.

-- 
Horms

Attachment: signature.asc
Description: Digital signature