[Pkg-netmeasure-discuss] Bug#889939: marked as done (separate scapy from scapy3k)
Debian Bug Tracking System
owner at bugs.debian.org
Thu Jun 7 22:42:05 BST 2018
Your message dated Thu, 07 Jun 2018 21:38:56 +0000
with message-id <E1fR2cS-000FhG-46 at fasolo.debian.org>
and subject line Bug#889939: fixed in scapy 2.4.0-2
has caused the Debian Bug report #889939,
regarding separate scapy from scapy3k
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.)
--
889939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889939
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Daniel Kahn Gillmor <dkg at fifthhorseman.net>
Subject: separate scapy from scapy3k
Date: Thu, 08 Feb 2018 17:55:46 -0500
Size: 3418
URL: <http://alioth-lists.debian.net/pipermail/pkg-netmeasure-discuss/attachments/20180607/14b9d433/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: irl at debian.org (Iain R. Learmonth)
Subject: Bug#889939: fixed in scapy 2.4.0-2
Date: Thu, 07 Jun 2018 21:38:56 +0000
Size: 5805
URL: <http://alioth-lists.debian.net/pipermail/pkg-netmeasure-discuss/attachments/20180607/14b9d433/attachment-0003.mht>
More information about the Pkg-netmeasure-discuss
mailing list