Bug#231538: *sigh*
GOTO Masanori wrote:
> > That would only help mips.
> >
> > I wonder what a mips machine would need with an i486 emulator.
> >
> > For IA-32 we would have to patch 2.4.18, but we cannot properly
> > update those packages in woody without people losing their
> > modules (would hurt a bit on laptops...). So that's a no-go.
>
> So you don't have any intenstion to install new 2.4 kernel with
> i486 emulation patch.
Exactly, since this would harm all notebook users.
> > Hence, the upgrade directory for real 80386 machines.
>
> What does it mean?
I thought that I've explained this already:
I have another solution to propose: Provide an upgrade-for-real-i386
directory, including a README and kernel packages to install before
upgrading to sarge. We've done a similar thing from bo->potato or
something.
This will require coordination with the release manager and the
ftpmasters to provide dists/sarge/main/upgrade-i386 which should
contain the kernel packages and a readme file.
> If there is no plan to support upgrade-path for i386 machines, then I
Nobody said that there is no plan to support an upgrade-path for i386
machines. We just cannot simply replace the kernel in the stable
distribution anymore due to fucked up dependencies and kernel
vulnerabilities.
> put the message "Use woody-proposed-updates 2.4.24 kernel" at
> libc6.preinst for 80386 machine. Then, we don't need to change the
> current woody kernels. I think it's the simplest fix. Is it OK?
No. Packages will eventually vanish from the proposed-updates
directory. We'll need an upgrade-i386 directory as we've had a couple
of releases before.
Regards,
Joey
--
Whenever you meet yourself you're in a time loop or in front of a mirror.
Please always Cc to me when replying to me on the lists.
Reply to: