Hello,
Wookey, on Sun 13 Nov 2016 19:57:51 +, wrote:
> OK. this worked for armhf and mips64el, but not for hurd-i386 because
> that is 'Failed' rather than 'Maybe-Failed'. I guess there is a way to
> force that, but I'm not sure what the right rune is (and I can't find
> the wb docs (again)
On 2016-11-13 18:06 +0100, Mattias Ellert wrote:
> Hi!
>
> The recent build of globus-gssapi-gsi 12.12-1 failed on
>
> - armhf
> - mips64el
> - hurd-i386
>
> This package depends on openssl, and there is currently a transition
> going on for that library. The build fails if some of the
On 2016-11-13 16:25 +, Javi Merino wrote:
> Hi,
>
> mercurial 4.0-1 failed to build on armhf because
> test-largefiles-update.t failed[0]. I've tested it on a porterbox ten
> times and I can't reproduce the error. Can you please give it back
> for armhf and see if it was a transient error
Hi!
The recent build of globus-gssapi-gsi 12.12-1 failed on
- armhf
- mips64el
- hurd-i386
This package depends on openssl, and there is currently a transition
going on for that library. The build fails if some of the package's
dependencies have not yet been rebuilt with the new openssl
Hi,
mercurial 4.0-1 failed to build on armhf because
test-largefiles-update.t failed[0]. I've tested it on a porterbox ten
times and I can't reproduce the error. Can you please give it back
for armhf and see if it was a transient error in the testsuite?
gb mercurial_4.0-1 . armhf
[0]
