Hi,
this came up in our dormant bugs checker ...
There was no reply from upstream yet, but I agree that a blunt revert might be
wrong unless they agree.
Sergio reached out, but probably needs to kindly ask again with some extra
noise.
--
You received this bug notification because you are a memb
Hi, this issue also happens when I try to run debootstrap for Jammy
arm64 on a Noble amd64 host. At the moment I use the workaround to use
ubuntu:jammy workers instead of ubunut:latest. It would be great if this
issue can be fixed soon.
--
You received this bug notification because you are a memb
FWIW, I left a comment on the bug report asking for guidance, because it
seems to me that just reverting the commit mentioned above isn't the
right solution (as we'd be reintroducing the bug fixed by the commit).
--
You received this bug notification because you are a member of qemu-
devel-ml, wh
I'm using quemu to tweak Armbian Jammy images for Raspberry Pi 5 (so it
would have ldconfig from 22.04) and I have signal 11 when libc
reconfiguration is triggered by apt.
What you may find interesting running the same process of updates on the
same base image on Ubuntu 22.04 (which has qemu 6.2)
** Changed in: qemu
Status: Unknown => New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/2072564
Title:
qemu-aarch64-static segfaults running ldconfig.real (amd64 host)
Status in QEMU:
Ne
** Also affects: qemu via
https://gitlab.com/qemu-project/qemu/-/issues/1913
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/2072564
Title:
qemu-aarch
