Bug#784604: systemd: can't remove systemd unless it is correctly running

[Michael Biebl]

Am 08.05.2015 um 14:19 schrieb Brian May:
> On Fri, 8 May 2015 at 21:34 Michael Biebl <biebl at debian.org> 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

Sorry, I didn't read that debian-devel thread.

> 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.

Ok, this particular issue, as mentioned earlier, is probably solved by
simply using "|| true" in the dpkg trigger. I think it's safe to ignore
errors from the dpkg trigger.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150508/33e9cf09/attachment-0002.sig>