Re: 01/02: gnu: libressl: Update to 2.5.3.

2017-04-19 Thread Ludovic Courtès
Mark H Weaver skribis: > Leo Famulari writes: > >> On Thu, Apr 13, 2017 at 05:08:29PM +0200, Ludovic Courtès wrote: >>> A simple approach is to force LibreSSL to always use its non-getentropy >>> code, and lift this restriction once we clearly require newer kernels¹. >>> The attached patch does

Re: 01/02: gnu: libressl: Update to 2.5.3.

2017-04-14 Thread Mark H Weaver
Leo Famulari writes: > On Thu, Apr 13, 2017 at 05:08:29PM +0200, Ludovic Courtès wrote: >> A simple approach is to force LibreSSL to always use its non-getentropy >> code, and lift this restriction once we clearly require newer kernels¹. >> The attached patch does that. >> >> Thoughts? > >> +

Re: 01/02: gnu: libressl: Update to 2.5.3.

2017-04-14 Thread Leo Famulari
On Fri, Apr 14, 2017 at 02:43:34PM +0200, Ludovic Courtès wrote: > I would suggest bumping the kernel requirement in glibc on the next > core-updates cycle (well, the current one!) and also making sure all our > build machines run the right thing. > > In the meantime, I’d apply the above hack, and

Re: 01/02: gnu: libressl: Update to 2.5.3.

2017-04-14 Thread Ludovic Courtès
Leo Famulari skribis: > On Thu, Apr 13, 2017 at 05:08:29PM +0200, Ludovic Courtès wrote: >> A simple approach is to force LibreSSL to always use its non-getentropy >> code, and lift this restriction once we clearly require newer kernels¹. >> The attached patch does that. >> >> Thoughts? > >> +

Re: 01/02: gnu: libressl: Update to 2.5.3.

2017-04-13 Thread Leo Famulari
On Thu, Apr 13, 2017 at 02:59:21PM -0400, Leo Famulari wrote: > On Thu, Apr 13, 2017 at 05:08:29PM +0200, Ludovic Courtès wrote: > > A simple approach is to force LibreSSL to always use its non-getentropy > > code, and lift this restriction once we clearly require newer kernels¹. > > The attached p

Re: 01/02: gnu: libressl: Update to 2.5.3.

2017-04-13 Thread Leo Famulari
On Thu, Apr 13, 2017 at 05:08:29PM +0200, Ludovic Courtès wrote: > A simple approach is to force LibreSSL to always use its non-getentropy > code, and lift this restriction once we clearly require newer kernels¹. > The attached patch does that. > > Thoughts? > + ;; Do as if 'getentropy' was m

Re: 01/02: gnu: libressl: Update to 2.5.3.

2017-04-13 Thread Ludovic Courtès
Leo Famulari skribis: > 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,

Re: 01/02: gnu: libressl: Update to 2.5.3.

2017-04-12 Thread Leo Famulari
On Wed, Apr 12, 2017 at 05:15:32AM -0400, Mark H Weaver wrote: > l...@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

Re: 01/02: gnu: libressl: Update to 2.5.3.

2017-04-12 Thread Mark H Weaver
l...@famulari.name (Leo Famulari) writes: > lfam pushed a commit to branch master > in repository guix. > > commit 69121e95cd5568238a0f207dfab708501ec4a753 > Author: Leo Famulari > Date: Tue Apr 11 13:09:03 2017 -0400 > > gnu: libressl: Update to 2.5.3. > > * gnu/packages/tls.scm (