[Debian-med-packaging] Bug#1071333: marked as done (pigx-rnaseq: FTBFS: ERROR: could not find report for SALMON at transcript level)

[Debian Bug Tracking System]

Your message dated Sat, 7 Sep 2024 14:49:57 +0200
with message-id <12b6ccf8-493b-4cf3-8d79-d69e1852ba2a at debian.org>
and subject line Re: pigx-rnaseq: FTBFS: ERROR: could not find report for SALMON at transcript level
has caused the Debian Bug report #1071333,
regarding pigx-rnaseq: FTBFS: ERROR: could not find report for SALMON at transcript level
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.)


-- 
1071333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071333
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Santiago Vila <sanvila at debian.org>
Subject: pigx-rnaseq: FTBFS: ERROR: could not find report for SALMON at transcript level
Date: Fri, 17 May 2024 22:39:42 +0200
Size: 62756
URL: <http://alioth-lists.debian.net/pipermail/debian-med-packaging/attachments/20240907/6b4702ba/attachment-0002.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: "Michael R. Crusoe" <crusoe at debian.org>
Subject: Re: pigx-rnaseq: FTBFS: ERROR: could not find report for SALMON at transcript level
Date: Sat, 7 Sep 2024 14:49:57 +0200
Size: 8075
URL: <http://alioth-lists.debian.net/pipermail/debian-med-packaging/attachments/20240907/6b4702ba/attachment-0003.eml>