Bug#661233: marked as done (vavoom: vlaunch cannot detect freedoom)

Wed Feb 29 03:51:06 UTC 2012

Your message dated Wed, 29 Feb 2012 03:47:40 +0000
with message-id <E1S2aVw-00022h-IX at franck.debian.org>
and subject line Bug#661233: fixed in vavoom 1.33-2
has caused the Debian Bug report #661233,
regarding vavoom: vlaunch cannot detect freedoom
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.)

-- 
661233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661233
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Paul Wise <pabs at debian.org>
Subject: vavoom: vlaunch cannot detect freedoom
Date: Sat, 25 Feb 2012 20:48:34 +0800
Size: 4411
URL: <http://lists.alioth.debian.org/pipermail/pkg-games-devel/attachments/20120229/b6450136/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: gustavo panizzo <gfa at zumbi.com.ar>
Subject: Bug#661233: fixed in vavoom 1.33-2
Date: Wed, 29 Feb 2012 03:47:40 +0000
Size: 5012
URL: <http://lists.alioth.debian.org/pipermail/pkg-games-devel/attachments/20120229/b6450136/attachment-0001.mht>