A small update. I seem to be getting weird installation issues left and right.
First, it was Kdenlive and not being able to use NVENC. Fixed using the flatpak version though. Thought the NVENC options in the Debian stable release were just dummied out Then it was WINE, seemingly installing correctly, but some features and menu entries weirdly seemed to be missing. Installing from the Popular Applications tab seemed to fix it though. Kind of... And then finally, what really made me suspicious, is that when I installed Virt-Manager, it didn't seem to install libvirtd. And when I look for QEMU and install it from either the MX Package Installer, Discover, or even apt-get as instructed by the QEMU site itself, it would only download the dummy file and NOTHING else.
Is this still me? Am I being stupid again? Is this just RC bugs? What is going on?
EDIT: Looking at the Debian package list on the official site again, it looks like libvirtd is not the correct "meta-package" name anymore. libvirt-daemon-system seems to be it. (
https://packages.debian.org/bullseye/virt-manager) Also, the usual qemu package one would download to get all the other necessary packages seems to have been phased out as well and turned into a dummy package that doesn't do anything. (
https://packages.debian.org/stable/qemu) So, the good news is, this doesn't seem to be an MX problem for those. The bad news is this is obviously incredibly frustrating. It's like, we've had these package names for years, and now suddenly, Debian's changing them all, and nobody has updated on their sites or the programs themselves what the package is ACTUALLY named in the repo anymore for fetching. And I wonder how far this goes too. How many packages are there that have been renamed but a package that depends on that package hasn't updated its dependency list at all?
Now, this is certainly not the end of the world, and in some cases like QEMU, it looks like they wanted to split up the main package and give users a choice of what versions they wanted. Nevertheless though, I just feel like Debian could have handled this better. I only found out the answer here myself because I'm a very persistent bastard. So many others might have just gotten super frustrated and given up entirely.