Bug#715647: marked as done ([Mayhem] Bug report on arpwatch: arpwatch crashes with exit status 139)

Sat May 13 13:15:04 UTC 2017

Your message dated Sat, 13 May 2017 15:13:00 +0200
with message-id <20170513151300.6a0b08c8 at localhost>
and subject line Re:  [Mayhem] Bug report on arpwatch: arpwatch crashes with exit status 139
has caused the Debian Bug report #715647,
regarding [Mayhem] Bug report on arpwatch: arpwatch crashes with exit status 139
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.)

-- 
715647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715647
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Alexandre Rebert <alexandre at cmu.edu>
Subject: [Mayhem] Bug report on arpwatch: arpwatch crashes with exit status 139
Date: Wed, 10 Jul 2013 11:23:20 -0400
Size: 40212
URL: <http://lists.alioth.debian.org/pipermail/pkg-security-team/attachments/20170513/e4f6bad1/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Lukas Schwaighofer <lukas at schwaighofer.name>
Subject: Re:  [Mayhem] Bug report on arpwatch: arpwatch crashes with exit status 139
Date: Sat, 13 May 2017 15:13:00 +0200
Size: 2922
URL: <http://lists.alioth.debian.org/pipermail/pkg-security-team/attachments/20170513/e4f6bad1/attachment-0003.mht>