So this shows two issues: * We need to put sysv-rc back into required, as long as we still have packages which only ship init.d scripts, so that they get proper /etc/rc?.d/ links.
* invoke-rc.d should stop looking at rc?.d links for systemd units, and rather check if *those* are enabled. -- 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/1587903 Title: invoke-rc.d does not start services in containers Status in Ubuntu Seeds: In Progress Status in init-system-helpers package in Ubuntu: In Progress Status in init-system-helpers source package in Yakkety: In Progress Bug description: In current yakkety, invoke-rc.d start is broken in containers: $ lxc launch images:ubuntu/yakkety/amd64 y1 $ lxc exec y1 systemctl stop cron $ lxc exec y1 invoke-rc.d cron start $ lxc exec y1 systemctl status cron ● cron.service - Regular background program processing daemon Loaded: loaded (/lib/systemd/system/cron.service; enabled; vendor preset: enabled) Active: inactive (dead) since Wed 2016-06-01 13:48:50 UTC; 9s ago "invoke-rc.d cron stop" does seem to work, though. This is a regression in recent yakkety. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: init-system-helpers 1.34ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 CurrentDesktop: i3 Date: Wed Jun 1 15:49:23 2016 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: init-system-helpers UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1587903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
