On Mon, Aug 19, 2019 at 11:41:33AM +0200, Bastien Durel wrote: > Ok, there muste have been an error somewhere ... > > root@corrin-2:~# apt-cache policy systemd-container > systemd-container: > Installed: (none) > Candidate: 241-5 > Version table: > 241-5 500 > 500 http://ftp.fr.debian.org/debian buster/main amd64 > PackagesPackages > root@corrin-2:~# dpkg -S /usr/bin/systemd-nspawn > dpkg-query: no path found matching pattern /usr/bin/systemd-nspawn
Are you saying that you installed systemd-nspawn from something other than a Debian package, *and* you put it in the /usr/bin directory? That's a really poor decision -- local add-ons should be in /usr/local or in /opt. Also, it appears you were relying on various dependenent packages, like dbus, without knowing it, since the thing that was actually using them wasn't installed via the packaging system. That's something you will have to track yourself. There's no way apt can do it for you. (It's also why I disable apt's autoremove features -- I don't ever want apt to decide I'm *not* using something, because I do have a bunch of local add-ons, and apt can't know what's actually safe to remove.)
