all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Olivier Dion via "Development of GNU Guix and the GNU System
	distribution." <guix-devel@gnu.org>
Cc: Julien Lepiller <julien@lepiller.eu>,
	 Olivier Dion <olivier.dion@polymtl.ca>
Subject: Re: GitLab to plans to delete dormant projects
Date: Sun, 07 Aug 2022 23:09:11 +0200	[thread overview]
Message-ID: <875yj3bw20.fsf@gnu.org> (raw)
In-Reply-To: <87iln5pgsh.fsf@laura> (Olivier Dion via's message of "Sat, 06 Aug 2022 10:50:38 -0400")

Hi,

Olivier Dion via "Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org> skribis:

> On Sat, 06 Aug 2022, Julien Lepiller <julien@lepiller.eu> wrote:
>> Our build farms need those sources, so they keep them in cache. If you
>> need a source, you can always substitute from the build farms if the
>> origin disappeared (that's actually the default and you don't even
>> need to trust the build farm for that to work).
>
> Does the cache as a time to live?  For example, would a source from 2020 in
> 20 years still be available on the build farms?  Or would the build
> farms make a request to Software Heritage?

Our build farms have limited capacity, so they probably won’t keep
everything forever, but that’s the mission of Software Heritage (SWH).

Guix automatically falls back to SWH for some time now, and SWH
archives all of gitlab.com, so I’m not very concerned:

  https://guix.gnu.org/en/blog/2019/connecting-reproducible-deployment-to-a-long-term-source-code-archive/

A shortcoming of our code, as Maxime mentions, is that it doesn’t
correctly handle retrieval of recursive checkouts from SWH.  That’s a
bug to fix, and there’s another one in this area:

  https://issues.guix.gnu.org/48540

> Okay great then.  Maybe it would be a good idea to test this by
> simulating the deletion of a Gitlab repo.  Better find it out now than
> when it's too late.

Other than checking whether ‘guix lint -c archival PKG’ complains, one
can run:

  guix build -S PKG --check

HTH!

Ludo’.


  reply	other threads:[~2022-08-07 21:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-06 13:08 GitLab to plans to delete dormant projects Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-08-06 14:34 ` Maxime Devos
2022-08-06 14:41 ` Julien Lepiller
2022-08-06 14:50   ` Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-08-07 21:09     ` Ludovic Courtès [this message]
2022-08-06 21:57 ` John Kehayias
2022-08-17 16:41 ` zimoun

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875yj3bw20.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=julien@lepiller.eu \
    --cc=olivier.dion@polymtl.ca \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.