unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 63634@debbugs.gnu.org
Subject: bug#63634: nar 404 leads to hard ‘guix substitute’ crash
Date: Mon, 22 May 2023 13:51:34 +0200	[thread overview]
Message-ID: <87y1lgy46x.fsf@gnu.org> (raw)
In-Reply-To: <87bkicfw6e.fsf@cbaines.net> (Christopher Baines's message of "Mon, 22 May 2023 12:02:04 +0100")

Christopher Baines <mail@cbaines.net> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:

[...]

>> BTW, ‘guix publish’ has provisions to not compress already-compressed
>> files, as in the case above.  We should really share code, Chris.
>
> I'm not sure if this is what you have in mind regarding code sharing,
> but I'll use compressed-file? from (guix utils) in the nar-herder to
> avoid generating cached compressions for these kind of files in the
> future.

Great, thank you.

Ideally we’d have a single ‘guix publish’ implementation, or at least
most of it would be a module shared by both ‘guix publish’ and
‘nar-herder’ because it’s tricky enough that we’d rather not have two of
them.  The (guix narinfo) module you introduced is a step in that
direction and as discussed earlier, we need to go further.

Ludo’.




  reply	other threads:[~2023-05-22 11:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-21 22:12 bug#63634: nar 404 leads to hard ‘guix substitute’ crash Ludovic Courtès
2023-05-22  8:00 ` Ludovic Courtès
2023-05-22  8:19 ` Simon Tournier
2023-05-22  9:36   ` Ludovic Courtès
2023-05-22 11:02     ` Christopher Baines
2023-05-22 11:51       ` Ludovic Courtès [this message]
2023-05-22  9:32 ` Ludovic Courtès
2023-05-22 10:59   ` Christopher Baines
2023-05-22 11:54     ` Ludovic Courtès
2023-05-22 15:35   ` Ludovic Courtès
2023-05-22 15:16 ` 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=87y1lgy46x.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=63634@debbugs.gnu.org \
    --cc=mail@cbaines.net \
    /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).