[Python-modules-team] Bug#878011: marked as done (yagv: Won't start. No module named future)

Debian Bug Tracking System owner at bugs.debian.org
Mon Oct 16 22:51:22 UTC 2017


Your message dated Mon, 16 Oct 2017 22:49:14 +0000
with message-id <E1e4ECA-000HId-Iy at fasolo.debian.org>
and subject line Bug#878011: fixed in pyglet 1.3.0~rc1-2
has caused the Debian Bug report #878011,
regarding yagv: Won't start. No module named future
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.)


-- 
878011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878011
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Rock Storm <rockstorm at gmx.com>
Subject: yagv: Won't start. No module named future
Date: Sun, 08 Oct 2017 16:46:49 +0200
Size: 3755
URL: <http://lists.alioth.debian.org/pipermail/python-modules-team/attachments/20171016/770ed123/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Yaroslav Halchenko <debian at onerussian.com>
Subject: Bug#878011: fixed in pyglet 1.3.0~rc1-2
Date: Mon, 16 Oct 2017 22:49:14 +0000
Size: 5535
URL: <http://lists.alioth.debian.org/pipermail/python-modules-team/attachments/20171016/770ed123/attachment-0001.mht>


More information about the Python-modules-team mailing list