>>>>> "Russ" == Russ Allbery <r...@debian.org> writes:
Yeah, but there's a significant factor that reduces things somewhat. In the past, /etc/init.d/foo failing would often cause postinst to break. However, in the past, there were a lot of failures that were not detected by the init.d script. We have two intentional decisions conflicting: 1) systemd tries to be a lot better about reporting service status than our previous infrastructure 2) We had the decision on a number of people to not hide failures by causing installation to fail. I actually think the folks in category 2 weren't typically hiding a lot of service failures, because it was fairly common for the init script to mask that, but it did tend to hide failures like missing configuration files etc. I certainly know that when deploying units for krb5 I had to mask a bunch more failures to get behavior consistent with the previous packages. Given the above, I think a discussion on -devel (which has happened) and a discussion on-policy is sufficient. --Sam
