[Touch-packages] [Bug 1691474] Re: invoke-rc.d service start fails on services with upstart-only scripts
I'm marking the main task as "Fix Released" as Ubuntu moved past upstart, so I believe this is not an issue anymore. Is this issue still relevant on Xenial? Marking the Xenial task a Incomplete for the moment. Tasks for EOL relases => Won't Fix. ** Changed in: init-system-helpers (Ubuntu Yakkety) Status: Confirmed => Won't Fix ** Changed in: init-system-helpers (Ubuntu Zesty) Status: Confirmed => Won't Fix ** Changed in: init-system-helpers (Ubuntu) Status: In Progress => Fix Released ** Changed in: init-system-helpers (Ubuntu Xenial) Status: Confirmed => Incomplete -- 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: Fix Released Status in init-system-helpers source package in Xenial: Incomplete Status in init-system-helpers source package in Yakkety: Won't Fix Status in init-system-helpers source package in Zesty: Won't Fix 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
[Touch-packages] [Bug 1691474] Re: invoke-rc.d service start fails on services with upstart-only scripts
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: init-system-helpers (Ubuntu Zesty) 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
[Touch-packages] [Bug 1691474] Re: invoke-rc.d service start fails on services with upstart-only scripts
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: init-system-helpers (Ubuntu Yakkety) 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
[Touch-packages] [Bug 1691474] Re: invoke-rc.d service start fails on services with upstart-only scripts
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
[Touch-packages] [Bug 1691474] Re: invoke-rc.d service start fails on services with upstart-only scripts
** Tags added: patch -- 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: New Status in init-system-helpers source package in Yakkety: New Status in init-system-helpers source package in Zesty: New 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
[Touch-packages] [Bug 1691474] Re: invoke-rc.d service start fails on services with upstart-only scripts
** Patch added: "init-system-helpers-xenial-lp1691474.debdiff" https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1691474/+attachment/4881468/+files/init-system-helpers-xenial-lp1691474.debdiff -- 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: New Status in init-system-helpers source package in Yakkety: New Status in init-system-helpers source package in Zesty: New 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
[Touch-packages] [Bug 1691474] Re: invoke-rc.d service start fails on services with upstart-only scripts
** Patch added: "init-system-helpers-yakkety-lp1691474.debdiff" https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1691474/+attachment/4881367/+files/init-system-helpers-yakkety-lp1691474.debdiff -- 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: New Status in init-system-helpers source package in Yakkety: New Status in init-system-helpers source package in Zesty: New 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
[Touch-packages] [Bug 1691474] Re: invoke-rc.d service start fails on services with upstart-only scripts
** Patch added: "init-system-helpers-zesty-1691474.debdiff" https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1691474/+attachment/4881359/+files/init-system-helpers-zesty-1691474.debdiff -- 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: New Status in init-system-helpers source package in Yakkety: New Status in init-system-helpers source package in Zesty: New 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
[Touch-packages] [Bug 1691474] Re: invoke-rc.d service start fails on services with upstart-only scripts
I have a patch I'll post in a bit. -- 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: New Status in init-system-helpers source package in Yakkety: New Status in init-system-helpers source package in Zesty: New 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