* Andreas Tille <andr...@an3as.eu>, 2014-09-25, 08:55:
The issue was then quickly solved upstream.
https://github.com/samtools/samtools/issues/300
I confirm that this problem is dealt with.
I the build log I see:
test/test.pl: module IO::Pty not found; skipping usage tests
Perhaps you should add libio-pty-perl to Build-Depends.
However, we remain at other errors which are potentially of the same
nature. If you have a look at the build log for i386[1] it ends up in
...
test_usage:
samtools
test_view:
Generating test data file .................. done
1: SAM -> BAM -> SAM
SAM files differ at /tmp/PHZ6a904Ap/view.test001.bam.sam : 34 /
/tmp/PHZ6a904Ap/view.001.sam : 34
Failed command:
/«PKGBUILDDIR»/samtools view -o /tmp/PHZ6a904Ap/view.test001.bam -b
/tmp/PHZ6a904Ap/view.001.sam && /«PKGBUILDDIR»/samtools view -h -o
/tmp/PHZ6a904Ap/view.test001.bam.sam /tmp/PHZ6a904Ap/view.test001.bam
.. failed ...
[...]
So it somehow gives the impression that on other arches (not only i386)
the terminal versus non-terminal environment remains at the unfortunate
state to cause errors in the test suite.
I don't know what is the source of these errors yet, but I don't think
it's about a missing tty. When I run the tests manually, I got the same
errors, even though all std{in,out,err} were a tty.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140925115130.ga3...@jwilk.net
