[Debian-med-packaging] Bug#966433: [Help] Re: seqan autopkg test failures triggered by gcc-defaults

[Andreas Tille]

Hi Michael,

On Fri, Aug 14, 2020 at 09:01:19AM +0200, Michael Crusoe wrote:
> I've got a fixed version of a release candidate of seqan3 3.0.2 in salsa.
> However it needs an updated range-v3 which has yet to be uploaded: see
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968053

If the new version you prepared would fix RC bug #966900 as well I'd
say go for an upload.
 
> I can upload the seqan3 3.0.2 release candidate with a code copy of the
> fixed range-v3, but as no packages build-depend on seqan3 I don't see the
> rush. Please feel free to correct my mis-understanding.

I agree that rush is not really needed.  However, our team has currently
lots of RC bugs and these create noise and developer time if the bug
report does not reflect the full story (specifically when different
people try to build this heavy package at the same time to check the
status.
 
Thanks a lot for your work on this

      Andreas.

-- 
http://fam-tille.de