Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: init-system-helpers (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1691474
Title:
invoke-rc.d service start fails on services with upstart-only scripts
Status in init-system-helpers package in Ubuntu:
In Progress
Status in init-system-helpers source package in Xenial:
Confirmed
Status in init-system-helpers source package in Yakkety:
Confirmed
Status in init-system-helpers source package in Zesty:
Confirmed
Bug description:
[Impact]
On 16.04+ if you using upstart as your primary init system "enabled" services
that _only_ have upstart scripts fail to start with invoke-rc.d (with a default
policy). This is problematic as #DEBHELPER# tokens in maintscripts rely on
invoke-rc.d to start/stop services and fail to start services on installation.
[Test Case]
Boot into affected system with upstart as default init.
Try starting an 'upstart only' service with 'invoke-rc.d service start'.
It is expected this should work.
[Regression Potential]
14.04/upstart behavior is that invoke-rc.d works, and 16.04/systemd also has
invoke-rc.d start working with enabled services and default policy.
16.04/upstart should be the same.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1691474/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
