Format: 1.8 Date: Tue, 26 Jul 2016 22:44:01 +0200 Source: init-system-helpers Binary: init-system-helpers dh-systemd init Architecture: all amd64 Version: 1.40 Distribution: yakkety-proposed Urgency: medium Maintainer: Launchpad Build Daemon Changed-By: Michael Biebl Description: dh-systemd - debhelper add-on to handle systemd unit files - transitional pack init - init metapackage init-system-helpers - helper tools for all init systems Closes: 830982 Changes: init-system-helpers (1.40) unstable; urgency=medium . [ Martin Pitt ] * update-rc.d: Add fallback if insserv is not available. If insserv is not available, we are either under systemd or a chroot, where the rc?.d/ link priorities don't matter, so create the /etc/rc?.d/[SK]01 links with a hardcoded "01" priority. Drop insserv dependency again. * invoke-rc.d: Add SysV fallback for "systemctl is-enabled". Version 1.35 switched to "systemctl is-enabled" to determine if a service is enabled. This also has worked for SysV init scripts since systemd 220-1 (via the systemd-sysv-install wrapper), but does not yet work under Jessie's systemd 215. Add a fallback to checking runlevel symlinks (for any runlevel) to fix upgrades where init-system-helpers gets upgraded before systemd, and to make i-s-h backportable to Jessie. (Closes: #830982) . [ Michael Biebl ] * invoke-rc.d: Drop fallback code for ancient upstart versions. Even wheezy ships a version >= 0.9.7. * invoke-rc.d: Only consider the enabled-state for start and restart. We should not deny other actions, like status, stop or reload on disabled services. * invoke-rc.d: Don't check the enabled state twice. On start|restart we already enforce the local policy and RC will be set to 101, if the service was disabled. Also, checking for the output of "systemctl --quiet is-enabled" is problematic, as it is currently broken for non-native services [1]. So drop it completely. [1] https://github.com/systemd/systemd/issues/3813 * invoke-rc.d: Allow restarting disabled-but-running services. Restart services that are disabled but have been started manually. A start request for a running service is a nop under systemd, so we don't need to handle start and restart separately. Checksums-Sha1: 2d463ffed1297909a8477208252f93b1ed26367a 5170 dh-systemd_1.40_all.deb 300955cb6ed8b2fe411bc7a3aa9b8f454b70df79 37406 init-system-helpers_1.40_all.deb 4b991fa2e21ed4bea8dd3dd7b706a01e5331f1f9 5194 init_1.40_amd64.deb Checksums-Sha256: dedc3c19ccaf8c0cc49dea7e2186f53186a1047eb034618b4855c2c499e65a77 5170 dh-systemd_1.40_all.deb 9643769e5961bb6e77e8d05afce459406ad8d04f36824c5d9e6ac513038685ed 37406 init-system-helpers_1.40_all.deb c6902aa7272c753a3aef86861d8f6450383fb22d6ca37aac299a775d8e63256b 5194 init_1.40_amd64.deb Files: a4c637f19161405b3e131bc59627094f 5170 oldlibs extra dh-systemd_1.40_all.deb 1172e707b1ff420c245bd007ca4cb646 37406 admin required init-system-helpers_1.40_all.deb 905bbc97e3518699d3d0b77632c0f1a2 5194 metapackages important init_1.40_amd64.deb