Your message dated Mon, 13 Oct 2014 21:39:33 -0700
with message-id 
<caczd_taesvqkp-aa+ee1qzdfjbqknt5b0hoou54xm2etszw...@mail.gmail.com>
and subject line Re: Bug#752854: 0ad: Re-enable upstream test suite
has caused the Debian Bug report #752854,
regarding 0ad: Re-enable upstream test suite
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 [email protected]
immediately.)


-- 
752854: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752854
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: 0ad
Version: 0.0.16-1
Severity: important
Tags: upstream
Control: forwarded -1 http://trac.wildfiregames.com/ticket/2488

Upstream test suite is disabled as of 0ad/0.0.16-1; #746822 just fixes the
runtime failure when built with gcc 4.9, but the test suite itself is still
broken (apparently because passing custom options to cxxtest is broken; see
upstream bug report).

This bug is just to remind myself to re-enable the test suite for the next
upstream release, and also so that I can just point people at this bug report
if I get nagged about it.

Regards,
Vincent

--- End Message ---
--- Begin Message ---
Version: 0.0.17-1

On Thu, Jun 26, 2014 at 7:23 PM, Vincent Cheng <[email protected]> wrote:
> Source: 0ad
> Version: 0.0.16-1
> Severity: important
> Tags: upstream
> Control: forwarded -1 http://trac.wildfiregames.com/ticket/2488
>
> Upstream test suite is disabled as of 0ad/0.0.16-1; #746822 just fixes the
> runtime failure when built with gcc 4.9, but the test suite itself is still
> broken (apparently because passing custom options to cxxtest is broken; see
> upstream bug report).
>
> This bug is just to remind myself to re-enable the test suite for the next
> upstream release, and also so that I can just point people at this bug report
> if I get nagged about it.

Forgot to close this bug in d/changelog, oops.

Regards,
Vincent

--- End Message ---

Reply via email to