Bug#978679: bedtools: autpkgtest failures

See https://alioth-lists.debian.net/pipermail/debian-med-packaging/2020-December/088479.html (subject "bedtools autopkgtest fails due to missing htsutil").

Bug#966470: fix for #966470: biobambam2 autopkgtest failures

Étienne Mollier wrote: > I had a look at the autopkgtest failure affecting biobambam2, > and since these segmentation faults were showing up only in my > autopkgtest environment, and not when using the package directly > on my system, it felt like a missing dependency. So I trapped > system calls

Bug#840974: samtools: FTBFS: configure.ac:69: error: macro PKG_CHECK_EXISTS is not defined; is a m4 file missing?

On Fri, Oct 21, 2016 at 12:01:26PM +0100, I wrote: > So the real solution here is to revert your autoconf-archive to 6dc6cc5^ > and use that unborked ax_with_curses.m4, which will in future be bundled > with samtools. This should have been 0351b06^. > On Thu, Oct 20, 2016 at 10:17:03PM +0200,

Bug#840974: samtools: FTBFS: configure.ac:69: error: macro PKG_CHECK_EXISTS is not defined; is a m4 file missing?

On Thu, Oct 20, 2016 at 10:17:03PM +0200, Sascha Steinbiss wrote: > I have pushed a fix (9aac9cb) to Git, solving the FTBFS. Before doing > an upload I would be very happy if an Autotools-savvy person could > take another closer look because admittedly I am not really sure about > the cause of the

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;

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 >