libsystemd0 is still installed, though.

Turns out apt depends on it?? coreutils depends on it??? None of those should have anything to do with systemd????

So what's up with that? Is there a way to actually remove libsystemd0 without breaking everything in half?

This bug report seems to indicate that libelogind0 at least used to Provides: libsystemd0, but it doesn't seem to anymore on our systems.

-- Ylfingr