Bug#551350: marked as done (arpwatch: Should the restart option also apply after general errors?)

Thu Jun 22 13:09:10 UTC 2017

Your message dated Thu, 22 Jun 2017 13:04:09 +0000
with message-id <E1dO1mM-000GHo-06 at fasolo.debian.org>
and subject line Bug#551350: fixed in arpwatch 2.1a15-4
has caused the Debian Bug report #551350,
regarding arpwatch: Should the restart option also apply after general errors?
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.)

-- 
551350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551350
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Stephen Kitt <steve at sk2.org>
Subject: arpwatch: Should the restart option also apply after general errors?
Date: Sat, 17 Oct 2009 17:24:34 +0200
Size: 4016
URL: <http://lists.alioth.debian.org/pipermail/pkg-security-team/attachments/20170622/f96500bc/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Lukas Schwaighofer <lukas at schwaighofer.name>
Subject: Bug#551350: fixed in arpwatch 2.1a15-4
Date: Thu, 22 Jun 2017 13:04:09 +0000
Size: 6607
URL: <http://lists.alioth.debian.org/pipermail/pkg-security-team/attachments/20170622/f96500bc/attachment-0001.mht>