Re: 2.6.14 status summary, and upcoming 2.6.15 ...

[dann frazier <dannf@dannf.org>]

On Tue, 2005-11-29 at 17:33 +0100, Sven Luther wrote:
> On Tue, Nov 29, 2005 at 01:13:16AM -0700, dann frazier wrote:
> > On Mon, 2005-11-28 at 04:12 +0100, Jonas Smedegaard wrote:
> > > > BTW, also, about ia64 situation, is it possible to use yaird in
> > > > initrd case still ? I know Eric was disabling this for 0.12, but we
> > > > are still using 0.11 ? 
> > > 
> > > Yaird 0.0.11 is newest release - so it _will_ be removed but _was_ not
> > > yet.
> > > 
> > > It is deprecated due to lack of testing. So if someone starts testing
> > > it then Erik might get convinced to keep it:
> > > Replace /etc/yaird/Templates.cfg
> > > with /usr/share/doc/yaird/examples/Debian-initrd.cfg.gz gunzipped
> > > should do the trick.
> > 
> > ia64 will work fine with yaird once a new elilo is uploaded - this is
> > planned for next week.  See #338185.
> 
> Ok, so the initramfs/ia64 problem was elilo related ? We can close that RC bug
> against linux-2.6 once this is done, right ? 

I reassigned it to elilo yesterday morning.

> > Though the above fix also gets us into a initramfs-tools provided
> > userspace, klibc seems to have a dynamic linker problem on ia64.  See
> > #341181.  Since sarge shipped with both 2.4 and 2.6 kernels for ia64, I
> > believe this leaves us with a broken upgrade path.
> 
> Yes, but a broken upgrade path for etch once released, we can propagate
> linux-2.6.14 to etch/testing for now though.

I'm not sure what the release policy is.  I don't personally have a
problem with it - I'll just keep debian-ia64 informed as things
progress.

> > I just discovered that 2.6.14-4 is not booting on ia64, while 2.6.14-3
> > did.  In fact, a rebuild of 2.6.14-3 on sid doesn't work either - looks
> > like a binutils problem.  2.6.15-rc2 seems to work fine w/ latest
> > binutils though.
> 
> Mmm, it seems that Pascal also has some trouble with 2.6.14-4 (altough self
> built one).

On ia64?  This bug turned out to be ia64-specific.  
This is #341257, for which a fix is pending in 2.6.14-5.