To add some data for your information: # dpkg -D100 --install /var/cache/apt/archives/linux-image-5.10.0-3-amd64_5.10.13-1_amd64.deb (Reading database ... 370596 files and directories currently installed.) Preparing to unpack .../linux-image-5.10.0-3-amd64_5.10.13-1_amd64.deb ... Unpacking linux-image-5.10.0-3-amd64 (5.10.13-1) over (5.10.12-1) ... D000100: setupvnamevbs main='/.' tmp='/..dpkg-tmp' new='/..dpkg-new' D000100: tarobject already exists D000100: tarobject directory exists D000100: setupvnamevbs main='/boot' tmp='/boot.dpkg-tmp' new='/boot.dpkg-new' D000100: tarobject already exists D000100: tarobject directory exists D000100: setupvnamevbs main='/boot/System.map-5.10.0-3-amd64' tmp='/boot/System.map-5.10.0-3-amd64.dpkg-tmp' new='/boot/System.map-5.10.0-3-amd64.dpkg-new' D000100: tarobject already exists D000100: tarobject file open size=83 D000100: tarobject file hash=e0a6c09212a19ed48183a052eab847e7 D000100: tarobject nondirectory, 'link' backup dpkg: error processing archive /var/cache/apt/archives/linux-image-5.10.0-3-amd64_5.10.13-1_amd64.deb (--install): unable to make backup link of './boot/System.map-5.10.0-3-amd64' before installing new version: Operation not permitted D000100: setupvnamevbs main='/boot/System.map-5.10.0-3-amd64' tmp='/boot/System.map-5.10.0-3-amd64.dpkg-tmp' new='/boot/System.map-5.10.0-3-amd64.dpkg-new' D000100: cu_installnew not restoring D000100: secure_remove '/boot/System.map-5.10.0-3-amd64.dpkg-new' unlink OK dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.10.0-3-amd64_5.10.13-1_amd64.deb
# ln System.map-5.10.0-3-amd64 System.map-5.10.0-3-amd64.bak ln: failed to create hard link 'System.map-5.10.0-3-amd64.bak' => 'System.map-5.10.0-3-amd64': Operation not permitted # mount | grep boot /dev/sda1 on /boot type vfat (rw,noatime,nodiratime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro) On Thu, 11 Feb 2021 20:04:39 +0100 Jan Luca Naumann <j.naum...@fu-berlin.de> wrote: > Package: dpkg > Version: 1.20.7.1 > Severity: important > > On EFI computer it is possible to use the ESP partition directly as > /boot. But dpkg has problems to upgrade packages, e.g. the linux-image > packages, then since it tries to create hardlinks as backup of existing > files. This is not supported for FAT32 partitions. > > dpkg should include some check if the target device systems may not > support hard links so /boot on FAT32 is supported.
