Your message dated Thu, 26 Apr 2018 14:14:34 -0400
with message-id 
<cao8golqhcssoxukrhplqpvejnvqlggpbohgh9ymamia4cgx...@mail.gmail.com>
and subject line Re: Bug#869655: approx frequently FTBFS with test failures
has caused the Debian Bug report #869655,
regarding approx frequently FTBFS with test failures
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 ow...@bugs.debian.org
immediately.)


-- 
869655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: approx
Version: 5.9-1
Severity: serious

Not sure whether there's a pattern when it fails
or whether tests fail randomly (and frequently):

https://buildd.debian.org/status/package.php?p=approx&suite=sid
https://tests.reproducible-builds.org/debian/history/approx.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/approx.html

--- End Message ---
--- Begin Message ---
Yes, the purpose of the 5.10 upload was to fix this problem, but I forgot
the "closes:" annotation.

On Thu, Apr 26, 2018 at 11:45 AM, Carsten Leonhardt <l...@debian.org> wrote:

> On Tue, 25 Jul 2017 14:36:03 +0300 Adrian Bunk <b...@debian.org> wrote:
> > Source: approx
> > Version: 5.9-1
> > Severity: serious
> >
> > Not sure whether there's a pattern when it fails
> > or whether tests fail randomly (and frequently):
> >
> > https://buildd.debian.org/status/package.php?p=approx&suite=sid
> > https://tests.reproducible-builds.org/debian/history/approx.html
> > https://tests.reproducible-builds.org/debian/rb-pkg/
> unstable/amd64/approx.html
>
> I don't see build failures for current version 5.10-1 in any of the
> referenced locations. Is there a reason to not close this bug?
>
>  - Carsten
>

--- End Message ---

Reply via email to