Lustre devel - Mar 2007 - [Bug 11931] Wrong directory for SLES 10 kernel download

Please don''t reply to lustre-devel. Instead, comment in Bugzilla by
using the following link:
https://bugzilla.lustre.org/show_bug.cgi?id=11931



(In reply to comment #1)
> The kernel tarball needs to be moved to where all of the other kernel
tarballs
> are: http://ftp.lustre.org/kernels/old.  That is where lbuild expects to
find
> _all_ kernels.  It would be silly (and prone to forgetfulness) to start
having
> to code a specific path for each kernel release made.      
No, all the other kernels are in
http://ftp.lustre.org/kernels/$CANONICAL_TARGET/old . 
http://ftp.lustre.org/kernels/old does not exist.  The problem is that
CANONICAL_TARGET ends up blank for sles 10.

Please don''t reply to lustre-devel. Instead, comment in Bugzilla by
using the following link:
https://bugzilla.lustre.org/show_bug.cgi?id=11931



(In reply to comment #2)
> 
> No, all the other kernels are in
> http://ftp.lustre.org/kernels/$CANONICAL_TARGET/old . 
> http://ftp.lustre.org/kernels/old does not exist.  The problem is that
> CANONICAL_TARGET ends up blank for sles 10.      
Ahhh.  Yes, I stand corrected.  Somebody didn''t update lbuild when they
committed the sles10 kernel support.  I actually forgot how that stuff works. 
:-/  They really shouldn''t have to though.  lbuild should not need 
updating
when a new target is added.  lbuild is one part of the build system that needs
to be refactored IMHO.

Please don''t reply to lustre-devel. Instead, comment in Bugzilla by
using the following link:
https://bugzilla.lustre.org/show_bug.cgi?id=11931

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED


(In reply to comment #3)
> Ahhh.  Yes, I stand corrected.  Somebody didn''t update lbuild when
they
> committed the sles10 kernel support.
Indeed.  It was updated on b1_4 but this change was never merged to any 1.6
branch:

Please don''t reply to lustre-devel. Instead, comment in Bugzilla by
using the following link:
https://bonsai.clusterfs.com/cvsview2.cgi?diff_mode=context&whitespace_mode=show&subdir=lustre-build&command=DIFF_FRAMESET&file=lbuild&rev1=1.31.2.3&rev2=1.31.2.4&root=/var/cvs/lustre/chroot/cvsroot/cfs

I have requested landing permission to merge this to HEAD and b_release_1_6_0.
> They really shouldn''t have to though.  lbuild should not need 
updating
> when a new target is added.  lbuild is one part of the build system that
needs
> to be refactored IMHO.      
I agree, and I''ll log a bug on the more general issue - hopefully it
can become
part of someone''s plan at some point.

Please don''t reply to lustre-devel. Instead, comment in Bugzilla by
using the following link:
https://bugzilla.lustre.org/show_bug.cgi?id=11931

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED


Fix landed on b_release_1_6_0 and HEAD.