Re: can't compile 2.4.24-benh

[Sven Luther <sven.luther@wanadoo.fr>]

On Sat, Jan 31, 2004 at 07:02:23PM +0100, Jens Schmalzing wrote:
> Hi,
> 
> Sven Luther writes:
> 
> > > # rsync -avz rsync.penguinppc.org::linux-2.4-benh linux-2.4.24-benh
> 
> You need to clean up this tree (with make-kpkg clean) before you use
> it.  BTW, where does it come from nowadays?  I always thought Ben
> switched to using the Bitkeeper tree a while ago.
> 
> > > then :
> > > 
> > > # cd linux-2.4.24-benh
> > > # grep RELEASE include/linux/version.h
> > > #define UTS_RELEASE "2.4.24-ben1"
> > 
> > Funny, by doing the same thing, i get : 
> > 
> > #define UTS_RELEASE "2.4.23-ben1"
> 
> > But no idea what actual bitkeeper changesets went into that.
> 
> AFAICT, there is no include/linux/version.h in the Bitkeeper tree, nor
> in Tom's rsync tree, nor in my rsync tree (which both pull directly
> from the Bitkeeper tree).
> 
> > Jens, do you have an idea on how to best take -benh snapshots ?
> 
> For personal use, I recommend one of the rsync trees, keeping in mind
> that you have to clean the one from penguinppc.org before use.  If you
> want something more fancy, you can clone the Bitkeeper tree, here is
> what I do on rsync.theorie.physik.uni-muenchen.de:

Well, i usually used to clone the linuxppc_2.4 bitkeeper tree, which had
nice tags for when the import was being done, but this tree was
silently obsoleted, and the new linuxppc-2.4 tree used, which lacks such
tags, especially for the 2.4.24 release, probably because the 2.4.24
release was done hastily.

Maybe it would be best to forget about 2.4.24, and extract the 2.4.23
from the -benh tree, if it is properly tagged, and backport the security
fix. Or maybe even backport the whole of Marcelo's 2.4.23->2.4.24 tag.

Friendly,

Sven Luther