[Debian-med-packaging] Bug#819617: Bug#819617: bcftools: FTBFS: test suite fails on several architectures

[Afif Elghraoui]

Hi, Andreas,

على الجمعـة 28 تشرين الأول 2016 ‫00:18، كتب Andreas Tille:
>> Upstream's planned solution to this requires some changes to their
>> format specification (details are in the upstream bug report). I think
>> we just have to wait.
> 
> The question is how long we have to wait.  We need to get our packages
> in testing into shape until the end of this year.  This bug is open for
> quite some time which makes me wonder how long the waiting time might
> be.
>  

I don't think it will be anytime soon. The planned changes seem to have
far-reaching consequences.


>>> Alternatively we could consider to document that some tests are failing
>>> on certain architectures and let those failed tests pass.
>>
>> I don't know if this is a good idea. The tests fail because inaccurate
>> results, not crashes. If we let these through, users on these
>> architectures would unsuspectingly get wrong output.
> 
> Yes, that's perfectly true and not my prefered solution.  The question
> was actually to those who have deeper insight and if its a matter of
> NaNs which have a different representation this might be some quite
> unusual corner case (on some rarely used architectures) and thus a
> proper documentation might make sense (or not - as I said depending on
> the expert insight into this issue).

I'm sorry about that. In this case, I think you should ask on the
upstream ticket (or see if the discussion between the upstream
developers there already answers your question).

>  
>> If we /really/ want to, we could make a different package for pysam's
>> bcftools interface. Reverse-dependencies that only need the samtools
>> interface could then be untethered from this bug. I wouldn't volunteer
>> to do this, though.
> 
> Any other volunteer?  I think if the problem persists until our advent
> bug squashing party I'll ask for removal of the packages for the
> affected architectures. 
> 

We'd need a new source package, not just a new binary package for the
pysam source code. I think you can expect for this bug not to be
resolved soon, so I see that it is either the pysam source-package copy
or the removal of rdeps on i386.

regards
Afif

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name