From: indieterminacy@libre.brussels
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Preservation of Guix 2021-10-22
Date: Mon, 25 Oct 2021 11:55:55 +0200 [thread overview]
Message-ID: <87o87dv2ya.fsf@qiuy04.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <86tuh58pfp.fsf@gmail.com>
Hi Simon,
Would it be remiss to cross reference contributors to these identified
scripts against Guix contributors (commits, ML messages)?
With that it may be possible to email them a templated message,
featuring:
* The current activity and reason for outreach
* The advantages of providing improvements
* A polite request for them (or interested parties) to assist (whenever)
possible
* A reference to documentation or cookbooks to provide further context
and approaches for resolving
WDYT?
Jonathan
zimoun <zimon.toutoune@gmail.com> writes:
> Hi,
>
> On Sat, 23 Oct 2021 at 11:55, Timothy Sample <samplet@ngyro.com> wrote:
>
>> Download the database (there’s a button at the bottom of the report),
>> and use SQLite to run the following queries.
>
> Cool! Thanks.
>
>
> If someone wants to help,
>
> $ wget https://ngyro.com/pog-reports/2021-10-22/pog.db
> $ guix environment --ad-hoc sqlite -- sqlite3
> sqlite> .open pog.db
> sqlite>
>
> then copy/paste that:
>
>> For the 376:
>>
>> SELECT fod_id,
>> swhid,
>> reference
>> FROM fods
>> LEFT JOIN fod_references USING (fod_id)
>> WHERE NOT is_in_swh
>> AND reference LIKE '(git-reference%';
>
> Therefore, I start with these ones. After this query, a quick Emacs
> macro to keep the URLs and then sort them to see if a pattern emerges.
> Nothing flashy. For the record, I get 214 GitHub URLs and 32 GitLab
> (.com) ones. I also note, among various stuff, that:
>
> "https://notabug.org/cwebber/guile-squee.git"
> "https://notabug.org/mothacehe/guile-squee.git"
>
> because one is defined at (gnu packages guile-xyz) by guile-squee and
> the other at (gnu packages ci) by guile-squee-dev. Then, other remark:
> Julia packages are listed:
>
> "https://github.com/JuliaArrays/OffsetArrays.jl"
> "https://github.com/JuliaArrays/StaticArrays.jl"
> "https://github.com/JuliaCI/BenchmarkTools.jl"
> "https://github.com/JuliaCollections/OrderedCollections.jl"
> "https://github.com/JuliaData/Parsers.jl"
> "https://github.com/JuliaDiff/ChainRules.jl"
> "https://github.com/JuliaDiff/ChainRulesCore.jl"
> "https://github.com/JuliaDiff/ChainRulesTestUtils.jl"
> "https://github.com/JuliaDiff/FiniteDifferences.jl"
> "https://github.com/JuliaGPU/Adapt.jl"
> "https://github.com/JuliaGraphics/ColorTypes.jl"
> "https://github.com/JuliaGraphics/Colors.jl"
> "https://github.com/JuliaLang/Compat.jl"
> "https://github.com/JuliaObjects/ConstructionBase.jl"
> "https://github.com/JuliaPackaging/JLLWrappers.jl"
> "https://github.com/JuliaWeb/URIs.jl"
>
> when I am sure to have scheduled them couple of days (weeks?) ago.
> Therefore, I have not investigated yet if the archiving failed or if POG
> is behind.
>
> Another general remark, some URLs are duplicated, for instance:
>
> "https://codeberg.org/dnkl/fcft"
> "https://git.cbaines.net/git/guix/build-coordinator"
> "https://git.code.sf.net/p/wsjt/wsjtx.git"
> "https://git.code.sf.net/u/bsomervi/hamlib.git"
> "https://git.elephly.net/software/mumi.git"
> "https://git.mfiano.net/mfiano/golden-utils"
> "https://git.sr.ht/~bzg/org-contrib"
> "https://git.systemreboot.net/guile-email"
> "https://git.systemreboot.net/guile-xapian"
> "https://git.umaneti.net/flycheck-grammalecte/"
> "https://github.com/Eloston/ungoogled-chromium"
> etc.
> …
>
> I have not checked if several packages refer to the same URL.
>
>
> Now, the core point. Running ’save-origin’ form (guix swh) on the URLs,
> I get for instance:
>
> https://code.divoplade.fr/mkdir-p.git accepted failed
> git://pumpa.branchable.com accepted failed
>
> for some I have checked. Investigation why they fails is required.
>
>
> Last, I failed to use TOKEN from “guix repl”. I just do:
>
> (use-modules (guix swh)
> (srfi srfi-1))
>
> (setenv "TOKEN"
> "eyJhb…"
> )
>
> (define missings
> (list
> "git://pumpa.branchable.com/"
>
> [...]
>
> "https://salsa.debian.org/installer-team/debootstrap.git"
> ))
>
> (for-each
> (lambda (url)
> (save-origin url))
> missings)
>
> but this fails. What do I miss? Does %swh-token need to be exported
> and tweaked in the script?
>
>
> Cheers,
> simon
next prev parent reply other threads:[~2021-10-25 10:04 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 [this message]
2021-10-25 11:19 ` zimoun
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
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=87o87dv2ya.fsf@qiuy04.i-did-not-set--mail-host-address--so-tickle-me \
--to=indieterminacy@libre.brussels \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.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).