Bug#231538: Bug status report?
At Tue, 9 Mar 2004 05:30:34 -0500,
Nathanael Nerode wrote:
> What progress has been made and what still needs to be done?
>
> Apparently current glibc now has the checking code in glibc to prevent it from
> being upgraded until *after* the kernel is upgraded (to 2.4.24 or 2.6.0).
I'm sorry that I don't still put the checking code. I put it after
checking build and test.
> However, as Karolina Lindqvist wrote:
> > You can't install 2.4.24 on a i386 system, since it depends on initrd-tools
> > (>= 0.1.48) and
> > modutils (>= 2.4.19) which are not in woody. The SID versions of those
> require
> > the new libc6, which in turn require the new kernel running. So how to
> > upgrade to that kernel on a 386?
>
> Andreas Barth wrote:
> >You add first
> >deb http://www.backports.org/debian stable initrd-tools module-init-tools
> >to your apt.sources-list and dist-upgrade only modutils and
> >initrd-tools. Afterwards, kernel, and afterwards the normal upgrade to
> >sarge.
>
> Obviously this is not really an acceptable upgrade path from woody to sarge!
> We do want to ensure an straighforward upgrade path from woody on real i386s.
AFAIK this problem was fixed. kernel-image-2.4.24-2-686
(2.4.24-2woody.1) is now available on woody. The thing which user
needs to do is only updating kernel 2.4.24, before upgrading to sarge.
> Andreas Barth wrote:
> >Well, to be plain, I think a more recent modutils and initrd-tools
> >should be added to woody with the next point release, and also a new
> >kernel image, both for the boot floppies and in the archive, that
> >emulates 486-opcodes on 386. Also this should be IMHO be noted in
> >the Release-notes.
>
> Is this the plan? This would require new packages in the next point release
> of woody, before sarge comes out, but I don't see that any progress has been
> made on that.
Well, I agree that release notes should describe about 386 problem
(386 processor machine needs to update its kernel 2.4.24 before
upgrading sarge). But... who should we report to?
Regards,
-- gotom
Reply to: