On Tue, 2016-05-31 at 16:15 -0400, Antoine Beaupré wrote: > On 2016-05-31 16:01:46, Hector Oron wrote: > > Hello, > > > > El 31 may. 2016 9:56 p. m., "Antoine Beaupré" <anar...@debian.org> escribió: > > > > > Hi, > > > > > > I still see this problem in debian jessie right now. I can't install the > > > linux kernel backport. > > > > > > cp: impossible d'évaluer « /boot/initrd.img-4.5.0-0.bpo.2-amd64 »: Aucun > > fichier ou dossier de ce type > > > > > > The initrd is simply not in the .deb: > > > > Initramfs binary is usually generated by a hook that calls an initramfs > > generator, from Debian, there is initramfs-tools or dracut. > > I see. Well, that doesn't seem to be working correctly. > > [1017]anarcat@angela:dist100$ sudo apt-get install > [sudo] password for anarcat: > Reading package lists... Done > Building dependency tree > Reading state information... Done > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 0 B of additional disk space will be used. > Setting up linux-image-4.5.0-0.bpo.2-amd64 (4.5.4-1~bpo8+1) ... > vmlinuz(/boot/vmlinuz-4.5.0-0.bpo.2-amd64 > ) points to /boot/vmlinuz-4.5.0-0.bpo.2-amd64 > (/boot/vmlinuz-4.5.0-0.bpo.2-amd64) -- doing nothing at > /var/lib/dpkg/info/linux-image-4.5.0-0.bpo.2-amd64.postinst line 256. > cp: cannot stat '/boot/initrd.img-4.5.0-0.bpo.2-amd64': No such file or > directory > Failed to copy /boot/initrd.img-4.5.0-0.bpo.2-amd64 to /initrd.img . [...]
Is your /boot directory on a VFAT filesystem or something else that doesn't support symlinks? Ben. -- Ben Hutchings Any sufficiently advanced bug is indistinguishable from a feature.
signature.asc
Description: This is a digitally signed message part
