unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 50327@debbugs.gnu.org
Subject: [bug#50327] [PATCH 0/2] Improved ‘free disk space’ message + a question
Date: Sat, 18 Sep 2021 11:55:06 +0200	[thread overview]
Message-ID: <87ee9mus1x.fsf@gnu.org> (raw)
In-Reply-To: <875yvkaymg.fsf@nckx> (Tobias Geerinckx-Rice's message of "Wed, 01 Sep 2021 21:05:42 +0200")

Hi,

Tobias Geerinckx-Rice <me@tobias.gr> skribis:

> This improves the warning given when free space looks sus.
>
> From:
>
>  note: build failure may have been caused by lack of free disk   space
>
> to:
>
>  note: only 0.01 MiB available in ‘/gnu/store’
>  note: only 5.00 MiB available in ‘/tmp/guix-build-foo.drv-0’
>  note: build failure may have been caused by lack of free disk   space
>
> It also raises the warning threshold from 8 to 64 MiB, which is a much
> prettier arbitrary integer.

LGTM.  :-)

Eventually we should i18n messages coming from the daemon.

> Question: shouldn't all of nix/ have licence headers added too? As it
> stands, there are two very lonely ones in
> nix/libstore/builtins.{cc,hh} and that's it.

Yeah well, they were taken as-is from Nix.  I wouldn’t bother,
especially since we wouldn’t what copyright holders to list in there.

Thanks!

Ludo’.




      parent reply	other threads:[~2021-09-18  9:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01 19:05 [bug#50327] [PATCH 0/2] Improved ‘free disk space’ message + a question Tobias Geerinckx-Rice via Guix-patches via
2021-09-01 19:25 ` [bug#50327] [PATCH 1/2] daemon: Print which disk(s) are how full Tobias Geerinckx-Rice via Guix-patches via
2021-09-01 19:25   ` [bug#50327] [PATCH 2/2] daemon: Suspect low disk space sooner Tobias Geerinckx-Rice via Guix-patches via
2021-09-18  9:53   ` [bug#50327] [PATCH 0/2] Improved ‘free disk space’ message + a question Ludovic Courtès
2021-09-18  9:55 ` Ludovic Courtès [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=87ee9mus1x.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=50327@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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).