From: Maxime Devos <maximedevos@telenet.be>
To: Olivier Dion <olivier.dion@polymtl.ca>, guix-devel@gnu.org
Subject: Re: GitLab to plans to delete dormant projects
Date: Sat, 6 Aug 2022 16:34:57 +0200 [thread overview]
Message-ID: <5317b0e4-2446-b1a9-a7c6-ec784bb74e90@telenet.be> (raw)
In-Reply-To: <87o7wxpliy.fsf@laura>
[-- Attachment #1.1.1: Type: text/plain, Size: 1038 bytes --]
On 06-08-2022 15:08, Olivier Dion via Development of GNU Guix and the
GNU System distribution. wrote:
> Hi,
>
> Following this article<https://lwn.net/Articles/903858/>, GitLab is
> planning to start deleting project that were idle for > 12 months.
>
> Many packages origin in Guix use an url to a GitLab project. What are
> the consequence of such deletion on Guix reproducibility? Will it
> affects the time-machine?
software heritage should avoid some problems, but from what I've heard
it doesn't support all edge cases yet (something about recursive
checkouts?).
I think it would be a good idea to make some Guile script to find all
GitLab git checkouts in Guix and run the swh linter on them to make sure
they are archived.
Additionally, it would be nice to support multiple URLs as fallbacks in
the 'origin' record for git-fetch (like we have for url-fetch) to avoid
the three points of failures (SWH and the copy at the substitute
servers) in the fallback mechanism.
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-08-06 14:35 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 [this message]
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
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
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=5317b0e4-2446-b1a9-a7c6-ec784bb74e90@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--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 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).