unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: gnutls 'name-constraints' test failure
Date: Tue, 19 Jul 2016 15:02:13 +0200	[thread overview]
Message-ID: <87shv5kch6.fsf@gnu.org> (raw)
In-Reply-To: <20160718171552.GA20926@jasmine> (Leo Famulari's message of "Mon, 18 Jul 2016 13:15:52 -0400")

Leo Famulari <leo@famulari.name> skribis:

> On Mon, Jul 18, 2016 at 12:48:55PM -0400, Leo Famulari wrote:
>> On Sun, Jul 17, 2016 at 01:33:34PM -0400, Leo Famulari wrote:
>> > Subject: [PATCH] gnu: gnutls: Fix test failure.
>> > 
>> > * gnu/packages/patches/gnutls-fix-stale-test.patch: New file.
>> > * gnu/local.mk (dist_patch_DATA): Add it.
>> > * gnu/packages/tls.scm (gnutls)[replacement]: New field.
>> > (gnutls/fixed): New variable.
>> 
>> Mark pointed out that using a graft won't work, since the ungrafted and
>> unpatched gnutls will still need to be built.

Bah, indeed!

> Unfortunately, the version of gnutls in core-updates (3.5.0) does not
> include the fix. It was introduced in 3.5.2.

So GnuTLS already doesn’t build on core-updates, right?  In that case,
we should go ahead an update it.

WDYT?

Thanks,
Ludo’.

  reply	other threads:[~2016-07-19 13:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-16 19:04 gnutls 'name-constraints' test failure nee
2016-07-17  7:32 ` Leo Famulari
2016-07-17 11:17   ` Andreas Enge
2016-07-17 13:25   ` Ludovic Courtès
2016-07-17 17:33     ` Leo Famulari
2016-07-18 12:14       ` Ludovic Courtès
2016-07-18 16:48       ` Leo Famulari
2016-07-18 17:15         ` Leo Famulari
2016-07-19 13:02           ` Ludovic Courtès [this message]
2016-07-19 17:05             ` Leo Famulari
2016-07-20  4:04               ` Leo Famulari
2016-07-20 10:07                 ` Ludovic Courtès
2016-07-18 17:30         ` Efraim Flashner
2016-07-19 13:01           ` gd on i686 Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87shv5kch6.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).