Bug#860963: marked as done (e2guardian does not start automatically at system startup)

Tue May 22 15:54:05 BST 2018

Your message dated Tue, 22 May 2018 14:51:16 +0000
with message-id <E1fL8dA-00074Z-Q2 at fasolo.debian.org>
and subject line Bug#860963: fixed in e2guardian 4.1.5-1
has caused the Debian Bug report #860963,
regarding e2guardian does not start automatically at system startup
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.)

-- 
860963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860963
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Peter Tuharsky <tuharsky at misbb.sk>
Subject: e2guardian does not start automatically at system startup
Date: Sat, 22 Apr 2017 20:46:00 +0200
Size: 3071
URL: <http://alioth-lists.debian.net/pipermail/debian-edu-pkg-team/attachments/20180522/1e332b4f/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Mike Gabriel <sunweaver at debian.org>
Subject: Bug#860963: fixed in e2guardian 4.1.5-1
Date: Tue, 22 May 2018 14:51:16 +0000
Size: 7103
URL: <http://alioth-lists.debian.net/pipermail/debian-edu-pkg-team/attachments/20180522/1e332b4f/attachment-0001.mht>