Bug#819040: marked as done (insserv: Symlinked init script in /etc/init.d/<service> fails to be recognised on reboot.)

[Debian Bug Tracking System]

Your message dated Wed, 23 Mar 2016 17:22:08 -0300
with message-id <CAAfdZj_iWPBq5zGbOvei148WSKxFxBkSk2KQp6zBoKuX1LQ_6g at mail.gmail.com>
and subject line Re: Bug#819040: insserv: Symlinked init script in /etc/init.d/<service> fails to be recognised on reboot.
has caused the Debian Bug report #819040,
regarding insserv: Symlinked init script in /etc/init.d/<service> fails to be recognised on reboot.
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 owner at bugs.debian.org
immediately.)


-- 
819040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819040
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Brett Ryan <brett.ryan at gmail.com>
Subject: insserv: Symlinked init script in /etc/init.d/<service> fails to be recognised on reboot.
Date: Wed, 23 Mar 2016 18:11:40 +1100
Size: 2677
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20160323/2bad75fc/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Felipe Sateler <fsateler at debian.org>
Subject: Re: Bug#819040: insserv: Symlinked init script in /etc/init.d/<service> fails to be recognised on reboot.
Date: Wed, 23 Mar 2016 17:22:08 -0300
Size: 4418
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20160323/2bad75fc/attachment-0001.mht>