From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Nicolas Graves <ngraves@ngraves.fr>, 62656@debbugs.gnu.org
Subject: bug#62656: broken guix time-machine + software-heritage
Date: Thu, 04 May 2023 15:05:44 +0200 [thread overview]
Message-ID: <878re4qmaf.fsf@inria.fr> (raw)
In-Reply-To: <CAJ3okZ0G2Jn41H+9pWskgo0eYOEpSB+GSggxz9Cr7dAZNSm1qg@mail.gmail.com> (Simon Tournier's message of "Thu, 4 May 2023 09:57:26 +0200")
Hi,
Simon Tournier <zimon.toutoune@gmail.com> skribis:
> On Thu, 4 May 2023 at 09:22, Ludovic Courtès <ludovic.courtes@inria.fr> wrote:
>
>> > Even if the bug on SWH would be fixed, at the rate the Guix repo is
>> > growing, it would be impractical to cook the whole Guix repo.
>>
>> Falling back to SWH to fetch channels is something we expect to be rare,
>> though.
>
> Being rare will not make it practical. ;-)
>
> What I am trying to point is that considering the size of the Guix
> repository and its rate, the current implementation will not scale and
> the fallback will be impossible for the end-user.
It’s not impossible, it just takes time (how long exactly, I don’t know,
we should check with the SWH folks what we can expect and what the
relevant factors are.)
That it takes time is acceptable IMO: we’re likely talking about
disaster recovery after the Savannah repo and its GitHub mirror have
disappeared.
Other channels, are typically smaller but also more likely to vanish; I
wonder how that affects the cooking time at SWH—again something to ask
them.
>> > And it appears to me weird when we, most of the time, need a very
>> > restricted set of commits.
>> >
>> > We could imagine to locally create a new repo (git init) and only add
>> > the content of the commit specified by “guix time-machine”.
>>
>> To do that we’d need to say goodbye to the features I mentioned above.
>
> Well, I do not see which features will be missing.
Those mentioned earlier, provenance tracking and downgrade detection in
particular.
Ludo’.
next prev parent reply other threads:[~2023-05-04 13:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 21:39 bug#62656: broken guix time-machine + software-heritage Nicolas Graves via Bug reports for GNU Guix
2023-04-04 10:51 ` Simon Tournier
2023-04-26 9:50 ` Ludovic Courtès
2023-04-26 10:01 ` Ludovic Courtès
2023-10-24 13:23 ` Simon Tournier
2023-04-28 14:43 ` Simon Tournier
2023-05-02 7:42 ` Ludovic Courtès
2023-05-02 18:01 ` Simon Tournier
2023-05-04 7:22 ` Ludovic Courtès
2023-05-04 7:57 ` Simon Tournier
2023-05-04 13:05 ` Ludovic Courtès [this message]
2023-05-04 17:00 ` Simon Tournier
2023-05-05 7:36 ` Ludovic Courtès
2024-02-04 13:03 ` bug#62656: close 62656 Nicolas Graves via Bug reports for GNU Guix
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=878re4qmaf.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=62656@debbugs.gnu.org \
--cc=ngraves@ngraves.fr \
--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).