[Python-modules-team] Bug#884669: marked as done (2to3 binary moved to it's own 2to3 package)

[Debian Bug Tracking System]

Your message dated Sun, 7 Jan 2018 14:10:37 +0100
with message-id <8f4a6471-5063-1bc2-dea7-915bd33846ef at googlemail.com>
and subject line Re: Bug#884669: 2to3 binary moved to it's own 2to3 package
has caused the Debian Bug report #884669,
regarding 2to3 binary moved to it's own 2to3 package
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.)


-- 
884669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884669
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Matthias Klose <doko at debian.org>
Subject: 2to3 binary moved to it's own 2to3 package
Date: Mon, 18 Dec 2017 11:14:36 +0100
Size: 2209
URL: <http://lists.alioth.debian.org/pipermail/python-modules-team/attachments/20180107/cc88411f/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Julian Taylor <jtaylor.debian at googlemail.com>
Subject: Re: Bug#884669: 2to3 binary moved to it's own 2to3 package
Date: Sun, 7 Jan 2018 14:10:37 +0100
Size: 5797
URL: <http://lists.alioth.debian.org/pipermail/python-modules-team/attachments/20180107/cc88411f/attachment-0001.mht>