On Mon, 2026-09-07 at 14:05 +0100, Jonathan Dowland wrote: > I find busybox-static incredibly useful for debugging running > containers: > > $ podman cp /usr/bin/busybox misbehaving-container:/bin/busybox > $ podman exec -ti misbehaving-container bash > # or if even bash isn't available, busybox sh > > and now I can use busybox to investigate the runtime state of the > container, without needing to know anything about what available libc > version (or even vendor) is inside, etc.
Given this and maybe similar use-cases, I propose a less radical change: Instead of removing busybox-static, keep the package, but rename the binary to busybox-static and drop the initramfs-tool hook. That way busybox and busybox-static will become co-installable. There are a few package that need to change their Depends/Recommends from "busybox | busybox-static" to just "busybox". -- Benjamin Drung Debian & Ubuntu Developer
