unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 46212@debbugs.gnu.org
Subject: bug#46212: ci.guix.gnu.org narinfos with excessive NarSize
Date: Mon, 22 Feb 2021 09:59:45 +0100	[thread overview]
Message-ID: <87blcciike.fsf@gnu.org> (raw)
In-Reply-To: <87blcgm6st.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 19 Feb 2021 16:11:14 +0100")


Hey Ludo,

> Did you eventually find out where the negative size comes from?
>
>   https://issues.guix.gnu.org/46212
>
> What should we do in your opinion with database entries that have a
> negative size?

I didn't look closely to this problem yet. However, I fixed an issue
with locales in the remote building mechanism that caused publish server
crashes:
https://lists.gnu.org/archive/html/bug-guix/2021-02/msg00231.html.

That's maybe somehow related.

Thanks,

Mathieu




  reply	other threads:[~2021-02-22  9:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31 14:47 bug#46212: ci.guix.gnu.org narinfos with excessive NarSize Christopher Baines
2021-01-31 15:20 ` Ludovic Courtès
2021-02-01  9:15   ` Ludovic Courtès
2021-02-19 15:11   ` Ludovic Courtès
2021-02-22  8:59     ` Mathieu Othacehe [this message]
2021-02-22 13:03       ` Ludovic Courtès
2021-02-24 10:26         ` Mathieu Othacehe
2021-02-01 19:57 ` Christopher Baines
2021-02-02 21:48   ` Ludovic Courtès
2021-03-21 14:38   ` Ludovic Courtès
2021-03-21 14:55     ` Ludovic Courtès
2021-03-21 14:55     ` Ludovic Courtès
2021-03-29  7:45       ` Mathieu Othacehe
2021-04-07  9:09 ` Brendan Tildesley via Bug reports for GNU Guix
2021-06-11 12:04 ` Christopher Baines
2021-06-18  9:48   ` Ludovic Courtès
2021-11-24 23:28     ` Ludovic Courtès
2021-11-25  8:42       ` Christopher Baines
2021-11-26 10:11         ` 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=87blcciike.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=46212@debbugs.gnu.org \
    --cc=ludo@gnu.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).