[Pkg-libvirt-maintainers] Bug#862279: closed by Guido Günther <agx at sigxcpu.org> (Re: Bug#862279: libvirt: virtlockd sysvinit script should source from /etc/default)

[Stefan Bader]

On 11.05.2017 08:57, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:libvirt package:
> 
> #862279: libvirt: virtlockd sysvinit script should source from /etc/default
> 
> It has been closed by Guido Günther <agx at sigxcpu.org>.
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Guido Günther <agx at sigxcpu.org> by
> replying to this email.
> 
> 
Yes, sorry. On its own this change makes not that much sense. It would need
these other 2 (one that creates a virtlockd init script based on the virtlogd
init script, and the other to install/ship it) to cause virtlockd to be started
with sysvinit the same as it is with systemd. This is just for completeness.
Feel free to ignore if that is not making sense for Debian.

Stefan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Add-sysvinit-script-for-virtlockd.patch
Type: text/x-diff
Size: 4942 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-libvirt-maintainers/attachments/20170511/606a3aa1/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-d-rules-dh_intallinit-virtlockd.patch
Type: text/x-diff
Size: 1141 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-libvirt-maintainers/attachments/20170511/606a3aa1/attachment-0001.patch>