On Sat, 2014-09-27 at 15:25 -0400, westlake wrote: > apt-get install linux-image-3.14-2-amd64<enter> and fails. But it works for me, so how am I supposed to know in what way it went wrong for you? > I suggest to close the bug because nobody is using a custom kernel. That is not true; many Debian users use custom kernels and generally initramfs-tools works for them. We do try to support custom kernels. > The > scripts are looking for /lib/modules/<kernel version> where kernel > version=="My unpackaged kernel that has been copied to /boot". And this > is the running kernel. They're not supposed to do that. I did find one instance where they do, and intend to fix it, but it only affects the way we find out what firmware files may be needed. > I already explained what I did to work around it so that apt-get does > not fail. Yes, but that doesn't tell us what went wrong. The error messages you sent were for an incorrect invocation of mkinitramfs, not for the package installation. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity.
Attachment:
signature.asc
Description: This is a digitally signed message part