unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: 27157@debbugs.gnu.org
Subject: bug#27157: Building Guile 2.2 "times out"
Date: Wed, 7 Jun 2017 16:35:57 -0700	[thread overview]
Message-ID: <CAN-vT6RCNMrCZjktAnaDmsV6nAaqJqtKy+Q1avG1ECH3KMB45g@mail.gmail.com> (raw)
In-Reply-To: <87poefqtem.fsf@netris.org>

[-- Attachment #1: Type: text/plain, Size: 607 bytes --]

Hi Mark,


> I pushed this as commit 1577a65809f8ef1883d18cf81095f632b65c042a.
> I'm not sure whether to close this bug or not.  Can someone else do so
> if appropriate?
>
>       Mark
>

I wanted to give another shot at removing the the default max-silent-time
options in our scripts, so that everything can be consistent, but haven't
got around it yet. I believe we shouldn't close this bug yet as it is still
possible to get into the problem by running "guix environment", for
example, which has a default max-silent-time value set to 1 hour.

Feel free to beat me to it if you have the bandwith.

Maxim

[-- Attachment #2: Type: text/html, Size: 987 bytes --]

      reply	other threads:[~2017-06-07 23:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-31  4:11 bug#27157: Building Guile 2.2 "times out" Maxim Cournoyer
2017-05-31 11:44 ` Ricardo Wurmus
2017-05-31 21:01   ` Ludovic Courtès
2017-06-01 16:06     ` Maxim Cournoyer
2017-06-01 21:37       ` Ludovic Courtès
2017-06-03 20:38         ` bug#27157: [PATCH] " Maxim Cournoyer
2017-06-03 21:37           ` Ludovic Courtès
2017-06-03 23:09             ` Maxim Cournoyer
2017-06-04 13:26               ` Ludovic Courtès
2017-08-31 13:19         ` Maxim Cournoyer
2017-09-01  9:10           ` Ludovic Courtès
2017-06-03  0:57   ` Mark H Weaver
2017-06-03  7:48     ` Ricardo Wurmus
2017-06-07 23:17       ` Mark H Weaver
2017-06-07 23:35         ` Maxim Cournoyer [this message]

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=CAN-vT6RCNMrCZjktAnaDmsV6nAaqJqtKy+Q1avG1ECH3KMB45g@mail.gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=27157@debbugs.gnu.org \
    --cc=mhw@netris.org \
    /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).