unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Timothy Sample <samplet@ngyro.com>
Cc: guix-devel@gnu.org
Subject: Re: Preservation of Guix Report 2021-12-06
Date: Tue, 07 Dec 2021 17:41:54 +0100	[thread overview]
Message-ID: <87fsr4icz1.fsf@gnu.org> (raw)
In-Reply-To: <87o85to67b.fsf@ngyro.com> (Timothy Sample's message of "Mon, 06 Dec 2021 14:59:20 -0500")

Hello,

Timothy Sample <samplet@ngyro.com> skribis:

>     <https://ngyro.com/pog-reports/2021-12-06/>
>
> Since the last report, I added many more reference categories and moved
> them to the database.  The new categories are 'hg', 'svn', 'cvs', 'bzr',
> 'tar-bz2', 'tar', 'zip', and 'text'.  Of these, only 'tar' and 'text'
> are being processed.  The rest are currently unsupported by my scripts.
> Moving the categories to the database allows me to make manual
> corrections when needed.  It also encouraged me to look through the
> references a bit more carefully to track down some of the weirder 'text'
> sources (like Bash patches) and fix up some other ones (in the style of
> “/tar_gz?download=yes”).

Good to see these additional details.

The SWH folks told me that plain files (like .el or .patch files) that
appear in ‘sources.json’ are currently not archived, but that this could
change.  So seeing 86% of them are archived is good news.

> I also made the fetching code more tenacious.  Now it uses the
> content-addressed mirrors from Guix and Nix to find regular files, and
> will recover “easy” Git references from SWH (“easy” means the commit is
> specified).

I suppose the scripts could use ‘url-fetch’, or even build the
fixed-output tarballs, to benefit from Guix’s fallback methods.
(Apologies if I’m stating the obvious.)

> The “disarchive” category is all the tarballs Disarchive failed to
> process.  An interesting thing here is that most of them are from Cargo.
> Long story short: older versions of Cargo used the “miniz”
> implementation of DEFLATE (rewritten in Rust) to compress tarballs.
> Disarchive doesn’t support this (yet...?).  There are 686
> old-Cargo-produced tarballs in the “disarchive” category.

Ah, I don’t want to hear about Rust!  ;-)

> One last thing to add is that the SWH folks were very quick to fix the
> loading error, so the increase in missing sources for recent commits is
> now gone.

Awesome.

Thanks for the update!

Ludo’.


  reply	other threads:[~2021-12-07 16:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06 19:59 Preservation of Guix Report 2021-12-06 Timothy Sample
2021-12-07 16:41 ` Ludovic Courtès [this message]
2021-12-07 18:33 ` 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=87fsr4icz1.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).