Your message dated Sat, 28 Dec 2013 13:32:33 -0800
with message-id <[email protected]>
and subject line Re: "Essential" package conflict between sysvinit and
systemd-sysv
has caused the Debian Bug report #645540,
regarding "Essential" package conflict between sysvinit and systemd-sysv
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
645540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645540
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Version: 2.88dsf-44
This has been fixed with the upload of sysvinit 2.88ds-44. Changelog entry:
sysvinit (2.88dsf-44) unstable; urgency=low
[ Roger Leigh ]
* initscripts:
- Mount pstore on /sys/fs/pstore (Closes: #722179).
[ Andrew Shadura ]
* initscripts:
- Use ifquery --state instead of parsing ifstate manually.
- Update Breaks for ifupdown.
[ Steve Langasek ]
* Move sysvinit functionality into a new binary package, sysvinit-core,
and have sysvinit depend on an ORed list of the available
implementations of /sbin/init. Since sysvinit is an Essential: yes
package, this is the only away to allow users to cleanly switch between
init systems without having to go through a multi-release-cycle
transition. Closes: #728566.
-- Steve Langasek <[email protected]> Thu, 26 Dec 2013 11:09:49 -0800
So systemd-sysv just needs the conflict updated on its side.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
[email protected] [email protected]
signature.asc
Description: Digital signature
--- End Message ---
_______________________________________________
Pkg-sysvinit-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
