lxc, waydroid not installable / qubes-kernel-vm-support has unnecessary dependency on busybox

[adrelanos]

Qubes OS release

R4.2

Brief summary

Attempting to install lxc or waydroid results in removal of of qubes-kernel-vm-support.

Steps to reproduce

sudo apt install lxc

Or.

Install waydroid.

Expected behavior

No such issue.

Actual behavior

https://forums.whonix.org/uploads/default/original/2X/1/17836bcc73cb49eb38f84da9dfea5a6915f23f7d.png

References

• https://forums.whonix.org/t/note-installing-waydroid-will-remove-busybox-which-is-a-dep-to-kicksecure-dependencies-cli/16910
• https://www.kicksecure.com/wiki/Waydroid

Additional information

Does qubes-kernel-vm-support really need to depend on busybox?

Would Depends: busybox | busybox-static be an acceptable alternative?

[marmarek]

Would Depends: busybox | busybox-static be an acceptable alternative?

I'm okay with this change, but I'm confused why it's necessary. busybox-static has Provides: busybox, so it shouldn't matter, no?

[marmarek]

In fact, the very similar issue was motivation of including that Provides: busybox - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375568.

[marmarek]

I just checked on my debian-12 system, the Provides: busybox does seem to work as expected:

user@d12test3:~$ dpkg -l qubes-kernel-vm-support
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                    Version        Architecture Description
+++-=======================-==============-============-=======================>
ii  qubes-kernel-vm-support 4.2.11+deb12u1 amd64        Qubes VM kernel and ini>
user@d12test3:~$ sudo apt install lxc
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  arch-test binutils binutils-common binutils-x86-64-linux-gnu busybox-static
  cloud-image-utils debootstrap distro-info fakechroot genisoimage libbinutils
  libctf-nobfd0 libctf0 libdistro-info-perl libdpkg-perl libfakechroot
  libfile-fcntllock-perl libgprofng0 liblxc-common liblxc1 libpam-cgfs
  libsubid4 lxc-templates lxcfs mmdebstrap rsync uidmap uuid-runtime wget
Suggested packages:
  binutils-doc mtools squid-deb-proxy-client ubuntu-archive-keyring shunit2
  wodim cdrkit-doc debian-keyring gcc | c-compiler bzr btrfs-progs python3-lxc
  qemu-user-static apt-transport-tor dpkg-dev genext2fs perl-doc qemu-user
  squashfs-tools-ng openssh-server python3-braceexpand
The following packages will be REMOVED:
  busybox
The following NEW packages will be installed:
  arch-test binutils binutils-common binutils-x86-64-linux-gnu busybox-static
  cloud-image-utils debootstrap distro-info fakechroot genisoimage libbinutils
  libctf-nobfd0 libctf0 libdistro-info-perl libdpkg-perl libfakechroot
  libfile-fcntllock-perl libgprofng0 liblxc-common liblxc1 libpam-cgfs
  libsubid4 lxc lxc-templates lxcfs mmdebstrap rsync uidmap uuid-runtime wget
0 upgraded, 30 newly installed, 1 to remove and 7 not upgraded.
Need to get 14.6 MB of archives.
After this operation, 77.8 MB of additional disk space will be used.

As you can see, only busybox is going to be removed, but not qubes-kernel-vm-support. Same happens on Whonix Workstation 17.

So, I cannot reproduce the issue.

[DemiMarie]

Is this issue specific to Debian oldstable/Whonix 16?

[adrelanos]

Is this issue specific to Debian oldstable/Whonix 16?

Could be.

So, I cannot reproduce the issue.

Confirmed for Whonix 17.

[marmarek]

Since Whonix 16 is EOL, this isn't relevant anymore.

[github-actions]

This issue has been closed as "not applicable." Here are some common examples of cases in which issues are closed as not applicable:

• Help and support requests (please see Help, support, mailing lists, and forum)
• Questions (please see Help, support, mailing lists, and forum)
• Discussion issues (please see Help, support, mailing lists, and forum)
• Bug reports for behavior that is already working as intended
• Enhancement requests to improve things that are already working as intended
• Issues that rest on mistaken assumptions or misunderstandings
• Issues that do not provide enough information
• Issues that are not actionable

We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community.

Regarding help and support requests, please note that this issue tracker (qubes-issues) is not intended to serve as a help desk or tech support center. Instead, we've set up other venues where you can ask for help and support, ask questions, and have discussions. By contrast, the issue tracker is more of a technical tool intended to support our developers in their work. We thank you for your understanding.

If anyone reading this believes that this issue was closed in error or that the resolution of "not applicable" is not accurate, please leave a comment below saying so, and we will review this issue again. For more information, see How issues get closed.