From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, "Timothy Sample" <samplet@ngyro.com>
Cc: guix-devel@gnu.org
Subject: Re: Preservation of Guix Report
Date: Fri, 22 Oct 2021 09:53:02 +0200 [thread overview]
Message-ID: <86ilxpzeap.fsf@gmail.com> (raw)
In-Reply-To: <87a6j2w1et.fsf@gnu.org>
Hi Ludo,
On Thu, 21 Oct 2021 at 22:47, Ludovic Courtès <ludo@gnu.org> wrote:
> ‘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.)
At package time, Guix uses tag. Then “guix lint” saves the upstream
repo; containing the correct tag. Now, upstream replaces in-place the
tag and saves to SWH by their own. How does SWH deal with this case?
Well, because it is not affordable to switch from the current
tag-address to immutable commit-address for defining packages, in order
to be 100% reliable, any fallback should use Disarchive-DB which stores
the mapping from checksum to swhid; for all kind origins.
Is it what you have in mind?
Cheers,
simon
next prev parent reply other threads:[~2021-10-22 7:55 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
2021-10-22 7:53 ` zimoun [this message]
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=86ilxpzeap.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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).