Le Thu, Jun 18, 2015 at 11:25:46PM -0400, Aaron M. Ucko a écrit :
I'm glad to see those platforms are doing better now, but that was only
part of the problem. There are still unexpected failures on i386 and
kfreebsd-i386 (though the count's dropped from 95 to 2, a big improvement):
found 762647 1.2-1
notfixed 762647 1.2-1
thanks
Charles Plessy ple...@debian.org writes:
since version 1.2-1 built fine on arm64 and ppc64el, I am closing this bug.
I'm glad to see those platforms are doing better now, but that was only
part of the problem. There are still unexpected failures
Charles Plessy ple...@debian.org writes:
failures on 32-bits platforms are expected to be fixed in the next upstream
release.
Glad to hear it!
I propose to wait for it. But if need is, it may be possible to backport the
patches.
I'm fine with waiting, just want the bug to stay open
This can be fixed on arm64 at least by fixed this bug in htslib:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770162
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Source: samtools
Version: 1.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
The builds of samtools for arm64 and ppc64el both failed because
the first samtools faidx test hit the autobuilders' activity timeout.
Given that these timeouts are
Le Tue, Sep 23, 2014 at 11:20:15PM -0400, Aaron M. Ucko a écrit :
The builds of samtools for arm64 and ppc64el both failed because
the first samtools faidx test hit the autobuilders' activity timeout.
Given that these timeouts are generous (300 minutes for arm64, 150 for
ppc64el), I suspect
Charles Plessy ple...@debian.org writes:
The other failures and timeouts are probably symptoms of non-portability
outside amd64. Some porters have contacted upstream on endianness issues, but
I do not know if the problem is likely to be solved in the short term.
Hi, Charles; thanks for the
7 matches
Mail list logo
