In #762194, the Technical Committee was asked to use its power under
-§6.1.4 to override the decision of the init package maintainers to
-depend on systemd-sysv as the first alternative dependency, thus
-ensuring both new installs and upgrades use systemd by default.
+§6.1.4 to override the transition plan of the init package maintainers
+to have both new installs and upgrades use systemd by default.
1. The CTTE determined in #727708 that systemd should be the default
init system in Debian.
-2. In <87mwc9gfsw.fsf@xoog.err.no>[1], the maintainers of the init
- package announced their transition plan for migrating to systemd as
- the default init system on both installs and new upgrades.
+2. In https://lists.debian.org/87mwc9gfsw.fsf@xoog.err.no, the
+ maintainers of the init package announced their transition plan for
+ migrating to systemd as the default init system on both installs
+ and new upgrades.
+
+3. The init package currently in jessie implements this transition.
==OPTION A==
a) Providing a fallback boot entry for sysvinit when systemd is the
default init in grub (#757298)
- b) Developing a mechanism to warn on non-standard inittab
- configurations which are unsupported in systemd.
+ b) Developing a mechanism to warn on inittab configurations which
+ are unsupported in systemd. (#761063)
- c) Providing documentation on how to opt to remain with sysvinit on
- both initial installs and upgrades.
+ c) Providing documentation on how to remain with sysvinit on
+ upgrades and swithc to sysvinit upon installation.
d) Numerous bug reports and fixes by contributors who have tested
the systemd migration in their configurations.
-
-
-1: https://lists.debian.org/87mwc9gfsw.fsf@xoog.err.no
+5. The CTTE advises (without overriding any Debian contributor,
+ maintainer, or team) that any such mitigations should be included
+ in jessie, to ensure a smooth transition for Debian users.