From: Leo Famulari <leo@famulari.name>
To: Myles English <mylesenglish@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: gnutls test failing during 'guix pull'
Date: Sun, 1 Jan 2017 15:47:16 -0500 [thread overview]
Message-ID: <20170101204716.GA11444@jasmine> (raw)
In-Reply-To: <87zijb6jzq.fsf@gmail.com>
On Sun, Jan 01, 2017 at 12:30:01PM +0000, Myles English wrote:
> Hello,
>
> I installed Guix 0.11.0 and I have tried a basic 'guix pull' to upgrade
> to 0.12.0 but it fails with the output below. Does anyone else have
> this problem? Can anyone tell me what to try to fix it?
>
> Thanks,
> Myles
>
> ============================================================================
> Testsuite summary for GnuTLS 3.4.7
> ============================================================================
> # TOTAL: 14
> # PASS: 11
> # SKIP: 2
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
> ============================================================================
> See tests/cert-tests/test-suite.log
Without seeing this log, I bet it's the same problem as this:
http://lists.gnu.org/archive/html/guix-devel/2016-07/msg00602.html
https://gitlab.com/gnutls/gnutls/commit/47f25d9e08d4e102572804a2aed186b01db23c65
Basically, the test suite relies on an a certificate that has expired.
I don't think you'll be able to build the package, or update Guix from
this point.
Are you using substitutes? If so, I guess we have deleted this old
substitute. In that case, I recommend installing 0.12.0 from scratch.
But maybe somebody else has a better idea...
next prev parent reply other threads:[~2017-01-01 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 12:30 gnutls test failing during 'guix pull' Myles English
2017-01-01 20:47 ` Leo Famulari [this message]
2017-01-01 21:15 ` Myles English
2017-01-03 9:46 ` 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=20170101204716.GA11444@jasmine \
--to=leo@famulari.name \
--cc=help-guix@gnu.org \
--cc=mylesenglish@gmail.com \
/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.
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).