Package: busybox
Version: 1:1.27.2-3
Severity: important
Hi,
Since a few days ago I am getting:
$ sudo update-initramfs -u -k all -v
Available versions: 4.18.0-2-amd64
Execute: /usr/sbin/update-initramfs -u -k "4.18.0-2-amd64" -b /boot -v
Keeping /boot/initrd.img-4.18.
Quoting Holger Wansing (2018-12-07 08:39:23)
> With commit
> "Replace ttf-freefont-udeb by fonts-freefont-udeb as the former has been
> removed from unstable (and thus testing)." under
> https://salsa.debian.org/installer-team/debian-installer/commit/94507f32b36ce050a3f45777b75dce793db3e614
> thin
On 07/12/2018 08:43, Chris Lamb wrote:
> If it helps:
>
> $ ls -l /usr/bin | grep busybox
> -rwxr-xr-x 1 root root 654,048 2018-07-13 05:19 busybox
>
> $ ls -l /bin | grep busybox
> lrwxrwxrwx 1 root root 16 2018-11-26 17:23 busybox -> /usr/bin/bu
Hi Chris,
> This is odd. The busybox package ships only a /bin/busybox binary, so
> I'm surprised to see your symlink to /usr/bin/busybox and the binary in
> there. Do you have any idea where that came from?
Well, I did attempt a usrmerge on this system; did it perhaps break
halfway through?
(Wh
Processing commands for cont...@bugs.debian.org:
> tags 915830 + moreinfo
Bug #915830 [busybox] busybox: cp: failed to access
'/var/tmp/mkinitramfs_h8da2B//usr/bin/busybox': Too many levels of symbolic
links
Added tag(s) moreinfo.
> severity 915830 normal
Bug #915830 [busybox] busybox: cp: faile
tags 915830 + moreinfo
severity 915830 normal
thanks
Chris Lamb wrote:
> Well, I did attempt a usrmerge on this system; did it perhaps break
> halfway through?
Purging and re-installing busybox fixed this for me; shall I close
this bug?
(Downgrading and tagging for now...)
Regards,
--
On 07/12/2018 12:27, Chris Lamb wrote:
> tags 915830 + moreinfo
> severity 915830 normal
> thanks
>
> Chris Lamb wrote:
>
>> Well, I did attempt a usrmerge on this system; did it perhaps break
>> halfway through?
>
> Purging and re-installing busybox fixed this for me; shall I close
> this bug?
Hi Chris,
> Well your symlink in /bin was dated 2018-11-26 17:23.
Ah, good spot!
> Your purge/reinstall could well fix it, just double-check you haven't
> ended up with *both* /bin/busybox and /usr/bin/busybox. You should have
> only the former and should be able to safely remove /usr/bin/busybo
[re-adding bugreport as cc]
Quoting Holger Wansing (2018-12-07 14:26:52)
> Jonas Smedegaard wrote:
> > Quoting Holger Wansing (2018-12-07 08:39:23)
> > > With commit
> > > "Replace ttf-freefont-udeb by fonts-freefont-udeb as the former has been
> > > removed from unstable (and thus testing)." un
On Fri, Dec 07, 2018 at 12:22:38AM +, Steve McIntyre wrote:
> I've no idea why he things this is a regression. But this is something
> we should probably change anyway - installing on RAID is pointlessly
> slow here unless you know how to work around it. And it's been that
> way since ~forever.
On Fri, Dec 07, 2018 at 10:11:02AM -0500, Lennart Sorensen wrote:
>On Fri, Dec 07, 2018 at 12:22:38AM +, Steve McIntyre wrote:
>> I've no idea why he things this is a regression. But this is something
>> we should probably change anyway - installing on RAID is pointlessly
>> slow here unless yo
Processing control commands:
> tag -1 pending
Bug #838503 [debian-installer] debian-installer: mdadm should not start syncing
RAID1 arrays at full speed during installation
Added tag(s) pending.
--
838503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838503
Debian Bug Tracking System
Conta
12 matches
Mail list logo
