On Fri, 8 May 2015 at 21:34 Michael Biebl <[email protected]> wrote: > I think the failure on uninstallation is just a red herring or just an > aspect of a bigger issue, i.e. your systemd installation is not fully > functional, most likely due to be run under OpenVZ (btw, it would have > been helpful to mention that in the bug report). > > Which kernel version is that? Does it satisfy all requirements as listed > in /usr/share/doc/systemd/README.gz? >
No. I think I already said this, didn't I? Please read the thread on debian-devel. I asked if I should file a bug report or not, and I was told Yes. https://lists.debian.org/debian-devel/2015/05/msg00013.html The problem isn't that systemd is broken, I know it is broken. The problem is that I know it is broken, but I can't remove it. Not everyone will be able to update the kernel, e.g. if using a 3rd party hosting provider, and don't won't to break their systems just because they forgot to disable installation of systemd. Like I said though, this doesn't affect me any more. After I upgrade me kernel I won't be able to reproduce the problem any more, and I won't be able to provide any more debugging information.
