Package: sysvinit Version: 2.88dsf-13.12 _Please_ resolve the "Essential" package conflict between sysvinit and systemd-sysv.
For those of us running testing/Wheezy or unstable/Sid with systemd, _every_single_time_ there is an upgrade - which can be approximately _every_single_day_ - something must be done to override the installation of sysvinit and the removal of systemd-sysv. The workarounds suggested at Debian Wiki systemd, http://wiki.debian.org/systemd#Issue_.231:_sysvinit_vs._systemd-sysv Section 4. Known Issues and Workarounds, neither is appropriate - "#1: Do not install systemd-sysv" or "#2: Install systemd-sysv and put package 'on hold'". Reviewing Debian Policy Manual, http://www.debian.org/doc/debian-policy/ch-binary.html Chapter 3 - Binary packages 3.6 Virtual packages 3.8 Essential packages and http://www.debian.org/doc/debian-policy/ch-relationships.html#s-virtual Chapter 7 - Declaring relationships between packages 7.4 Conflicting binary packages - Conflicts 7.5 Virtual packages - Provides 7.6 Overwriting files and replacing packages - Replaces Consider agreeing upon some "virtual package", say "init", and having Package: sysvinit Provides: init Conflicts: init Replaces: init Essential and Package: systemd-sysv Provides: init Conflicts: init Replaces: init Essential It seems to me that the Debian sysvinit maintainers must be the ones to "pick up the ball" here and offer a solution. James -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
