Bug#1012318: marked as done (diffoscope 214 produced no output and was killed after running into timeout after 150m)

[Debian Bug Tracking System]

Your message dated Wed, 8 Jun 2022 15:50:28 +0200
with message-id <YqCpJBlKUKNXFLQ5 at mapreri.org>
and subject line Re: Bug#1012318: diffoscope 214 produced no output and was killed after running into timeout after 150m
has caused the Debian Bug report #1012318,
regarding diffoscope 214 produced no output and was killed after running into timeout after 150m
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.)


-- 
1012318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012318
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Roman Lebedev <lebedev.ri at gmail.com>
Subject: diffoscope 214 produced no output and was killed after running into timeout after 150m
Date: Sat, 04 Jun 2022 01:05:18 +0300
Size: 7674
URL: <http://alioth-lists.debian.net/pipermail/reproducible-builds/attachments/20220608/2afbcec7/attachment.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Mattia Rizzolo <mattia at debian.org>
Subject: Re: Bug#1012318: diffoscope 214 produced no output and was killed after running into timeout after 150m
Date: Wed, 8 Jun 2022 15:50:28 +0200
Size: 5865
URL: <http://alioth-lists.debian.net/pipermail/reproducible-builds/attachments/20220608/2afbcec7/attachment-0001.eml>