unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Our git just broke
Date: Sun, 14 Aug 2016 21:08:10 -0400	[thread overview]
Message-ID: <87zioealfp.fsf@netris.org> (raw)
In-Reply-To: <20160814161308.GA1197@jasmine> (Leo Famulari's message of "Sun, 14 Aug 2016 12:13:08 -0400")

Leo Famulari <leo@famulari.name> writes:

> On Sun, Aug 14, 2016 at 02:28:43PM +1000, Ben Woodcroft wrote:
>> On 14/08/16 03:28, Pjotr Prins wrote:
>> > Also gnutls does not pass it's tests on my system, nor does
>> > subversion.
>> Both gnutls and subversion are substituted for me on current master
>> (891284), indicating they built without issue OK on hydra. Does it still not
>> work for you?
>
> Regarding GnuTLS, I assume Pjotr is describing the failure of the
> "name-constraints" test [0].
>
> Unfortunately, GnuTLS used a certificate in one of their tests without
> taking care to handle its expiration date, so now the certificate has
> expired. It looks like a mistake. Other test certificates in their test
> suite are guarded against this, and they have committed a fix.

Yes.  Unfortunately we cannot fix this with a graft, because that does
not prevent the original build from being performed, and if that
original build consistently fails after a certain date, I don't see a
straightforward way to work around that.

While repopulating hydra's store after the failure of its RAID array,
I resorted to temporarily setting the system clock back on the mips64el
build machine to repeat that build.

It might be worth investigating the possibility of setting the system
clock to a deterministic value within build containers.

       Mark

  reply	other threads:[~2016-08-15  1:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-13 12:41 Our git just broke Ben Woodcroft
2016-08-13 13:07 ` Leo Famulari
2016-08-13 13:23   ` Vincent Legoll
2016-08-13 13:32   ` Ben Woodcroft
2016-08-13 15:33   ` ng0
2016-08-13 23:11     ` Leo Famulari
2016-08-13 15:36   ` ng0
2016-08-13 23:11     ` Leo Famulari
2016-08-14  2:46       ` Eric Bavier
2016-08-14 18:24   ` Our git just broke [PATCH]: gnu: Add stagit, adjust version-control.scm ng0
2016-08-17 11:38     ` ng0
2016-08-13 17:28 ` Our git just broke Pjotr Prins
2016-08-14  4:28   ` Ben Woodcroft
2016-08-14 16:13     ` Leo Famulari
2016-08-15  1:08       ` Mark H Weaver [this message]
2016-08-15 11:23         ` Ben Woodcroft
2016-08-15 17:11           ` Leo Famulari
2016-08-15 18:04             ` Pjotr Prins

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=87zioealfp.fsf@netris.org \
    --to=mhw@netris.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).