Your message dated Sat, 23 Feb 2019 20:07:40 +0000
with message-id <e1gxdae-0003w1...@eggs.gnu.org>
and subject line Re: [Pkg-sysvinit-devel] Bug#570756: repeated "insserv: 
warning: current stop runlevel(s) ..."
has caused the Debian Bug report #570756,
regarding repeated "insserv: warning: current stop runlevel(s) ..."
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.)


-- 
570756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
X-debbugs-CC: rcc...@packages.debian.org
Package: initscripts
Version: 2.87dsf-8.1
Severity: wishlist

We rcconf users now see
Setting up initscripts (2.87dsf-8.1) ...
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `ntp' 
overwrites defaults (empty).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `ntp' 
overwrites defaults (empty).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `ntp' 
overwrites defaults (empty).
about 20 times upon upgrade



--- End Message ---
--- Begin Message ---
[2019-02-22 03:55] 積丹尼 Dan Jacobson <jida...@jidanni.org>
> part       text/plain                 294
> >>>>> "DB" == Dmitry Bogatov <kact...@debian.org> writes:
> >> Suddenly the message is now being repeated twenty etc. times. Once was 
> >> enough.
> DB> I guess the issue is somehow related to dependency-based boot migration.
> DB> Does bug manifest itself in modern installations?
> Seems OK now. Thanks.

Thank you for prompt response. Closing.
-- 
        Note, that I send and fetch email in batch, once every 24 hours.
                 If matter is urgent, try https://t.me/kaction
                                                                             --

--- End Message ---

Reply via email to