> native upstart jobs seem to just ignore not being able to connect to upstart
No, they do not. There are various stock maintainer script snippets that will ignore these failures on the maintainer script's behalf, but:
a) this removes an important feedback channel about other problems that cause services to fail to start on package upgrade
b) it prevents running any services in chroots, which up to now has been supported.
> native upstart jobs seem to just ignore not being able to connect to upstart
No, they do not. There are various stock maintainer script snippets that will ignore these failures on the maintainer script's behalf, but:
a) this removes an important feedback channel about other problems that cause services to fail to start on package upgrade
b) it prevents running any services in chroots, which up to now has been supported.