From: zimoun <zimon.toutoune@gmail.com>
To: indieterminacy@libre.brussels
Cc: guix-devel@gnu.org
Subject: Re: Preservation of Guix 2021-10-22
Date: Mon, 25 Oct 2021 13:19:21 +0200 [thread overview]
Message-ID: <86wnm173nq.fsf@gmail.com> (raw)
In-Reply-To: <87o87dv2ya.fsf@qiuy04.i-did-not-set--mail-host-address--so-tickle-me>
Hi Jonathan,
On Mon, 25 Oct 2021 at 11:55, indieterminacy@libre.brussels wrote:
> Would it be remiss to cross reference contributors to these identified
> scripts against Guix contributors (commits, ML messages)?
I do not understand what you are asking?
The only thing contributors can do is “./pre-inst-env guix lint
<package>” before they submit. Then, «we» are investigating why the
coverage is not 100% and are trying to address the blockers (from Guix
infra first, then ask SWH).
It is an experimental work-in-progress. It seems too early for
cross-reference something – it is already enough work without digging
commits or ML messages. :-)
Where people can help is by exploring the current pog.db file and check
against SWH; as Timothy or I are trying here or there, for example.
Or people can also help by subscribing to Software Heritage
Authentication service [1], get a TOKEN, and run systematically:
$ GUIX_SWH_TOKEN=$TOKEN guix lint -c archival
Well, for sure, it is a poor man solution. But it helps to improve the
coverage waiting a robust mechanism. :-) For instance, one can run,
--8<---------------cut here---------------start------------->8---
$ TOKEN=eyJh…
$ for p in $(guix package -p ~/.guix-profile -I | cut -f1);\
> do GUIX_SWH_TOKEN=$TOKEN guix lint -c archival $p \
> ;done
--8<---------------cut here---------------end--------------->8---
for all the profiles they use. For instance, it should display
something like:
--8<---------------cut here---------------start------------->8---
gnu/packages/emacs-xyz.scm:21700:5: emacs-rust-mode@1.0.0: scheduled Software Heritage archival
gnu/packages/emacs-xyz.scm:18966:5: emacs-org-re-reveal@3.12.1: scheduled Software Heritage archival
gnu/packages/emacs-xyz.scm:12296:5: emacs-org-contrib@0.3: scheduled Software Heritage archival
gnu/packages/emacs-xyz.scm:12264:5: emacs-org@9.5: source not archived on Software Heritage and missing from the Disarchive database
gnu/packages/emacs-xyz.scm:786:5: emacs-magit@3.3.0: scheduled Software Heritage archival
gnu/packages/guile.scm:317:12: guile@3.0.7: source not archived on Software Heritage and missing from the Disarchive database
gnu/packages/emacs.scm:80:12: emacs@27.2: source not archived on Software Heritage and missing from the Disarchive database
gnu/packages/mail.scm:1352:12: notmuch@0.33.2: source not archived on Software Heritage and missing from the Disarchive database
gnu/packages/aspell.scm:115:12: aspell-dict-en@2020.12.07-0: source not archived on Software Heritage and missing from the Disarchive database
--8<---------------cut here---------------end--------------->8---
Then, people can go to
<https://archive.softwareheritage.org/save/#requests>
and check if the «scheduled» packages «succeeded». Please report if the
status is «failed». Because it requires investigations.
1: <https://archive.softwareheritage.org/oidc/login/>
Cheers,
simon
next prev parent reply other threads:[~2021-10-25 11:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 1:09 Preservation of Guix 2021-10-22 Timothy Sample
2021-10-23 7:52 ` zimoun
2021-10-23 15:55 ` Timothy Sample
2021-10-25 8:43 ` zimoun
2021-10-25 9:55 ` indieterminacy
2021-10-25 11:19 ` zimoun [this message]
2021-10-25 20:49 ` zimoun
2021-10-29 14:25 ` Ludovic Courtès
2021-10-25 21:51 ` zimoun
2021-10-26 13:12 ` Timothy Sample
2021-10-26 15:50 ` zimoun
2021-10-29 14:30 ` Ludovic Courtès
2021-10-30 16:00 ` 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=86wnm173nq.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=indieterminacy@libre.brussels \
/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.