On Thu, Dec 21, 2006 at 04:44:07PM -0800, Kevin B. McCarty wrote: > > Hence there is currently *no way* to upgrade Sarge -> Etch without the > package manager insisting to remove the running kernel package! > Ouch.
> Possible fixes: > > 1) Fix #395181 so initrd-tools can get back into Etch > 2) Make available 2.4.27/2.6.8 kernel images for a new Sarge point > release that don't depend on initrd-tools Except that this assumes someone has upgraded to the latest point release. I understand that the upgrade problem is critical, but I don't think this sort of functionality can be added in a point release and then legitimately assumed to be present by the Etch installer. I think you must assume that the person will have some previous version of the kernel with the dependency still in place. Besides, I think that releasing new kernel packages requires lots of work from the kernel team. > 3) Make available udev and/or yaird packages built against the Sarge libc6 > 4) Remove the initrd-tools conflict from libc6 in Etch (might not work > due to #364338) > 5) Others? > Introduce a dummy initrd-tools in Etch which conflicts with +1 to the Debian version of Etch's libc6? That way at the first security update to libc6 or the release of Lenny (whichever comes first) the package will be forcibly removed anyway. Another possibility would be to have it depend on exactly the version of libc6 Etch releases with. Regards, -Roberto -- Roberto C. Sanchez http://people.connexer.com/~roberto http://www.connexer.com
signature.asc
Description: Digital signature
