Your message dated Sun, 10 Aug 2014 12:24:40 -0400
with message-id <53e79cc8.70...@gmail.com>
and subject line Re: [sysvinit-core] Incorrect priority (required)
has caused the Debian Bug report #754338,
regarding [sysvinit-core] Incorrect priority (required)
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 ow...@bugs.debian.org
immediately.)
--
754338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sysvinit-core
Version: 2.88dsf-53.2
Severity: serious
X-Debbugs-Cc: bi...@debian.org
X-Debbugs-Cc: 754...@bugs.debian.org
sysvinit-core's priority field presents it as required. While I never tried
running a Debian system without it or its predecessor, it would appear that
sysvinit-core is not / no longer required. The hints I have observed to that
effect are the conflict declared by systemd-sysv, Michael Biebl's intervention
in #754059, as well as a conflict declared by upstart, as pointed out by
Michael.
--
Filipus Klutiero
http://www.philippecloutier.com
--- End Message ---
--- Begin Message ---
Version: 2.88dsf-55.3
Hi Michael,
On 2014-08-10 05:15, Michael Biebl wrote:
Hi,
this is not a bug in the sysvinit(-core) package, but rather the archive
priorities needing to be updated.
It *is* a bug (at least) in sysvinit even properly speaking... but it *will* be
fixed when 2.88dsf-55.3 makes it to testing.
I filed [1] to get the priorities of sysvinit and sysvinit-core adjusted.
Thanks
Closing this bug report.
Michael
[1] bugs.debian.org/cgi-bin/bugreport.cgi?bug=757650
--
Filipus Klutiero
http://www.philippecloutier.com
--- End Message ---
