Bug#822701: [Debian-med-packaging] Bug#822701: Bug#822701: samtools: FTBFS: UNEXPECTED PASS: Task worked when we expected failure;

On 1 Jun 2016, at 05:25, Afif Elghraoui wrote: > I sincerely apologize that this comes across as offensive-- it truly > wasn't intended that way. I was (and still am) somewhat confused about > this subject, thoug. My confusion is mostly about the tightness of the >

Bug#822701: [Debian-med-packaging] Bug#822701: Bug#822701: samtools: FTBFS: UNEXPECTED PASS: Task worked when we expected failure;

I was hoping someone would be able to explain these to me. Should I have been reporting bugs upstream when these happened? I did not press my questions before because I hadn't before got around to digging up the logs. على الثلاثاء 31 أيار 2016 ‫21:25، كتب Afif Elghraoui: > The first version of >

Bug#822701: [Debian-med-packaging] Bug#822701: Bug#822701: samtools: FTBFS: UNEXPECTED PASS: Task worked when we expected failure;

Hi, John, على الثلاثاء 31 أيار 2016 ‫03:01، كتب John Marshall: > On Mon, 2 May 2016 21:54:49 -0700 Afif Elghraoui wrote: >> This seems to happen with every htslib upgrade in the past few releases. >> bcftools builds have also been breaking as a result and I was a little >>

Bug#822701: [Debian-med-packaging] Bug#822701: Bug#822701: samtools: FTBFS: UNEXPECTED PASS: Task worked when we expected failure;

On Mon, 2 May 2016 21:54:49 -0700 Afif Elghraoui wrote: > This seems to happen with every htslib upgrade in the past few releases. > bcftools builds have also been breaking as a result and I was a little > confused. Aren't backwards-compatibility breaks supposed to be indicated >

Bug#822701: [Debian-med-packaging] Bug#822701: Bug#822701: samtools: FTBFS: UNEXPECTED PASS: Task worked when we expected failure;

Hi, Charles, I'm sorry for my late reply على الثلاثاء 26 نيسـان 2016 ‫21:38، كتب Charles Plessy: > Le Wed, Apr 27, 2016 at 10:12:31AM +0900, Charles Plessy a écrit : >> >> Perhaps we also need htslib 1.3.1 to "Break" samtools < 1.3.1... I cloned >> this bug to address that issue. > > Hi all, >