Control: forcemerge 163988 -1 Control: tags -1 wontfix Hi!
On Tue, 2016-05-31 at 12:32:23 -0400, Arthur Moore wrote: > Package: dpkg > Version: 1.18.7 > dpkg attempts to create a hardlink to the old versions before updating > kernel files in /boot. > In order to use `bootctl` without special options /boot is a FAT32 EFI > partition that does not support hardlinks. > This results in dpkg being unable to proceed. > > $apt-get update > ... > dpkg: error processing archive > /var/cache/apt/archives/linux-image-4.5.0-2-amd64_4.5.5-1_amd64.deb > (--unpack): > unable to make backup link of './boot/System.map-4.5.0-2-amd64' before > installing new version: Operation not permitted > dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) > Errors were encountered while processing: > /var/cache/apt/archives/linux-image-4.5.0-2-amd64_4.5.5-1_amd64.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) Yes, this is a required feature dpkg expects from the filesystem to be able to operate safely. > Given that the `bootctl` expects /boot to be a FAT32 EFI partition and many > guides are starting to recommend it, this bug will become even > more prevalent as time goes on. That seems very ill-advised. What current packages in Debian do when dealing with EFI booting, is to create a /boot/efi directory where the FAT32 EFI partition is mounted, and then any required files are installed there using one of the kernel hook scripts. > I suggest dpkg use a fallback mechanism, like file renaming, when hard > linking fails for file backups. Doing this preceisely for the /boot files would be extremely dangerous as an abrupt shutdown or system crash could render the system unbootable, so I'm marking this as wontfix. In your case this can be fixed in a similar way as other similar packages supporting EFI have done. Thanks, Guillem
