Your message dated Thu, 12 Oct 2017 23:54:49 +0200
with message-id <[email protected]>
and subject line Re: Bug#825945: kernel update fails with /boot as a FAT32 EFI
partition
has caused the Debian Bug report #825945,
regarding dpkg: Please support installation of hardlinkful packages on
hardlinkless FS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
825945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825945
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libc6
Version: 2.2.5-14.3
Severity: important
Hi,
I want to install Debian on AFS, but AFS doesn't support hard links
across directories. So libc6 isn't installable and the whole system, too.
dpkg --fsys-tarfile libc6_2.2.5-14.3.deb | LANG=C tar vt | grep 'link to'
Could you replace these hard links by symlinks? Or tell how can I remove
these from the package at installation time?
Joerg.
-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux joerg 2.4.19 #1 Son Aug 11 11:35:10 MEST 2002 i586
Locale: LANG=de_DE, LC_CTYPE=de_DE
Versions of packages libc6 depends on:
ii libdb1-compat 2.1.3-4 The Berkeley database routines [gl
--- End Message ---
--- Begin Message ---
Hi!
On Sun, 2016-06-12 at 20:10:29 +0200, Guillem Jover wrote:
> Control: forcemerge 163988 -1
> Control: tags -1 wontfix
> 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.
I added this requirement in
<https://wiki.debian.org/Teams/Dpkg/FAQ#Q:_What_are_the_filesystem_requirements_by_dpkg.3F>
with references to these bugs. Closing the report.
Thanks,
Guillem
--- End Message ---
