From: "Ludovic Courtès" <ludo@gnu.org>
To: Timothy Sample <samplet@ngyro.com>
Cc: guix-devel@gnu.org
Subject: Re: Preservation of Guix Report
Date: Thu, 21 Oct 2021 22:47:22 +0200 [thread overview]
Message-ID: <87a6j2w1et.fsf@gnu.org> (raw)
In-Reply-To: <87o87jjx54.fsf@ngyro.com> (Timothy Sample's message of "Wed, 20 Oct 2021 15:48:07 -0400")
Hi Timothy!
Timothy Sample <samplet@ngyro.com> skribis:
> Early this summer I did a bunch of work trying to figure out which Guix
> sources are preserved by the SWH archive. I’m finally ready to share
> some preliminary results!
>
> https://ngyro.com/pog-reports/2021-10-20/
>
> This report is already quite outdated, though. It only covers commits
> up to the end of May, and sometime in June is when the sources were
> checked against the SWH archive. I’m sharing it now to avoid any
> further delays.
This is truly awesome! (Did you manage to grab all that info with the
default rate limit?!)
I can’t wait for the updated report now that Simon and yourself have
identified that SWHID computation bug!
Some of our <git-reference> refer to tags, not commits. How do you
determine whether they’re saved?
‘guix lint -c archival’ uses ‘lookup-origin-revision’, which is a good
approximation, but it’s not 100% reliable because tags can be modified
and that procedure only tells you that a same-named tag was found, not
that it’s the commit you were expecting. (And really, we should stop
referring to tags.)
Thank you! 👍🏽
Ludo’.
next prev parent reply other threads:[~2021-10-21 20:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 19:48 Preservation of Guix Report Timothy Sample
2021-10-21 2:04 ` Timothy Sample
2021-10-21 7:39 ` zimoun
2021-10-21 16:26 ` Timothy Sample
2021-10-22 7:58 ` zimoun
2021-10-21 20:47 ` Ludovic Courtès [this message]
2021-10-22 7:53 ` zimoun
2021-10-29 14:12 ` Mutable Git tags & Software Heritage Ludovic Courtès
2021-10-30 16:19 ` zimoun
2021-11-09 16:55 ` Ludovic Courtès
2021-10-22 14:19 ` Preservation of Guix Report Timothy Sample
2021-10-22 17:32 ` Timothy Sample
2021-10-29 14:20 ` 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=87a6j2w1et.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=samplet@ngyro.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).