On Wed, Apr 12, 2017 at 05:15:32AM -0400, Mark H Weaver wrote:
> leo@famulari.name (Leo Famulari) writes:
> >     gnu: libressl: Update to 2.5.3.
> >     
> >     * gnu/packages/tls.scm (libressl): Update to 2.5.3.
> 
> This failed to build on Hydra on both x86_64 and i686 (the only builds
> that have been attempted so far):
> 
>   https://hydra.gnu.org/build/1976679  (x86_64)
>   https://hydra.gnu.org/build/1976657  (i686)

The failures look like this:

[...]
FAIL: arc4randomforktest.sh
PASS: asn1test
PASS: base64test
../test-driver: line 107:  6370 Killed                  "$@" > $log_file 2>&1
FAIL: bntest
PASS: bftest
PASS: asn1time
PASS: bytestringtest
PASS: chachatest
../test-driver: line 107:  6397 Killed                  "$@" > $log_file 2>&1
FAIL: cipherstest
../test-driver: line 107:  6402 Killed                  "$@" > $log_file 2>&1
FAIL: cipher_list
../test-driver: line 107:  6410 Killed                  "$@" > $log_file 2>&1
[...]

This is libressl-portable bug #290:

https://github.com/libressl-portable/portable/issues/290

There is a problem with using getentropy() or getrandom() from
glibc-2.25 with Linux < 3.17, when these syscalls where introduced.
Basically, glibc will return ENOSYS, which applications are not handling
properly.

I expect the build to succeed on armhf, where I believe the builders
have kernels > 3.17.

In the case of libressl, the developers have closed as WONTFIX, although
perhaps they could be persuaded to make libressl handle ENOSYS somehow.

Cpython hit the same problem, and they worked around it. This means that
the Python interpreters Hydra builds for x86_64 and i686 not use the new
getentropy() / getrandom() syscalls, even though many Guix users and
probably all GuixSD users have more recent kernels:

https://bugs.python.org/issue29157

Can we disable the build on Hydra without marking the package as
non-substitutable?