From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: 69058-done@debbugs.gnu.org
Subject: bug#69058: Failure when fallback to Disarchive+SWH
Date: Mon, 12 Feb 2024 14:15:00 +0100 [thread overview]
Message-ID: <875xytg6y3.fsf@inria.fr> (raw)
In-Reply-To: <87plx17s9c.fsf@gmail.com> (Simon Tournier's message of "Mon, 12 Feb 2024 13:59:27 +0100")
Hi,
Simon Tournier <zimon.toutoune@gmail.com> skribis:
>> Fixed in 1610a632d4b3097282d18af27ff3e9e178d7dfcb.
>
> Cool! Thanks.
>
> However, it means that it stays broken for all commits before this fix,
> right? Somehow, if only SWH is available, then
>
> guix time-machine -C channels.scm -- shell -m manifest.scm
>
> will fail for all channels older than today. Right?
Mostly, yes (“mostly” because derivations using “builtin:git-download”
will automatically be fixed once we’ve updated the ‘guix’ package, but
that only helps if you’re traveling to after September 2023 (commit
13b0cf85eb31e1b1ea674debbbfb0f35a32d1374).
> For instance, redoing your ReScience paper from 2020 using only SWH as I
> did [1] some months ago is now broken (because a change on SWH side).
Indeed. :-/
That’s a real bummer, but that’s the nature of software: we cannot
retroactively fix bugs.
> Well, I am fine to keep this bug closed but for the posterity we need
> something like:
>
> guix swh get -C channels.scm -m manifest.scm
Exactly! We have the demonstration of just how important that is.
Ludo’.
next prev parent reply other threads:[~2024-02-12 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 17:21 bug#69058: Failure when fallback to Disarchive+SWH Simon Tournier
2024-02-11 18:11 ` Simon Tournier
2024-02-12 10:28 ` Ludovic Courtès
2024-02-12 11:24 ` Ludovic Courtès
2024-02-12 12:59 ` Simon Tournier
2024-02-12 13:15 ` Ludovic Courtès [this message]
2024-02-12 14:04 ` Simon Tournier
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=875xytg6y3.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=69058-done@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).