On Friday 06 March 2009, Marco d'Itri wrote: > On Mar 05, Frans Pop <elen...@planet.nl> wrote: > > The problem seems to be that depmod, which is run as part of the > > build, generates a modules.dep file with incomplete paths. These > > incomplete paths in turn cause initramfs-tools to create a broken > > initrd. > > Upstream says this is a feature, and actually it is documented in the > changelog. > If path[0] != '/' then the path is relative to the kernel directory.
That does not really explain *why* the behavior was changed. and IMO it's an extremely unfortunate backwards compatibility issue. I also don't think changing initramfs-tools is sufficient to fix this. It is very much possible that someone builds a new kernel package on a system running unstable/testing and thus having the new m-i-t, but wants to install it on a system running stable that has the old intramfs-tools. As the initramfs is created at package installation time, a reboot will still fail in that case. For the same reason fixing the upstream kernel Makefile is no solution as that would only fix the problem for new kernel versions. IMO m-i-t will need to ensure backwards compatibility for the forseeable future (at least until lenny is archived) to avoid major problems for users. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
