Bug#915830: busybox: cp: failed to access '/var/tmp/mkinitramfs_h8da2B//usr/bin/busybox': Too many levels of symbolic links
- To: Chris Lamb <firstname.lastname@example.org>, email@example.com
- Cc: Ben Hutchings <firstname.lastname@example.org>
- Subject: Bug#915830: busybox: cp: failed to access '/var/tmp/mkinitramfs_h8da2B//usr/bin/busybox': Too many levels of symbolic links
- From: Axel Beckert <email@example.com>
- Date: Wed, 8 May 2019 00:27:01 +0200
- Message-id: <[🔎] firstname.lastname@example.org>
- Reply-to: Axel Beckert <email@example.com>, firstname.lastname@example.org
- In-reply-to: <1544347454.2343811.1603522144.5094D8B6@webmail.messagingengine.com>
- References: <email@example.com> <firstname.lastname@example.org> <email@example.com> <1544347454.2343811.1603522144.5094D8B6@webmail.messagingengine.com> <firstname.lastname@example.org>
> cp: failed to access '/var/tmp/mkinitramfs_mSMoqa//usr/bin/busybox': Too many levels of symbolic links
> E: /usr/share/initramfs-tools/hooks/zz-busybox failed with return 1.
I'm having a very similar issue which makes me think that this is a
more generic issue and not necessarily busybox-specific:
update-initramfs: Generating /boot/initrd.img-4.19.0-4-686-pae
cp: failed to access '/var/tmp/mkinitramfs_URATxd//usr/bin/touch': Too many levels of symbolic links
E: /usr/share/initramfs-tools/hooks/fsprotect failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.19.0-4-686-pae with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-4.19.0-4-686-pae (--configure):
installed linux-image-4.19.0-4-686-pae package post-installation script subprocess returned error exit status 1
Note that it's /usr/bin/touch and
/usr/share/initramfs-tools/hooks/fsprotect, but otherwise looks like
the same issue.
>From my point of view this looks like either an issue in
initramfs-tools or in both, busybox and fsprotect (and maybe more)
packages not having adapted to breaking changes in initramfs-tools.
Chris Lamb wrote:
> Whilst you could indeed change this, given that my attempt at usrmerge
> failed for reasons unrelated to busybox and/or initramfs generation
JFTR: My case is on a non-usrmerge i386 system running Sid. The issue
shows up for at least a few weeks now if not longer (hadn't touched
that system for a few weeks or so beforehand) and seemingly for all
kernels installed or upgraded since it appeared the first time.
> Thus, we should probably just close this bug.
If I wouldn't have found this bug report, I'd have filed (and might
still file) the above as at least severity serious as it breaks the
installation/upgrade of more or less unrelated packages.
,''`. | Axel Beckert <email@example.com>, https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE