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 (PoG) report 2023-03-13
Date: Thu, 16 Mar 2023 17:41:34 +0100	[thread overview]
Message-ID: <87v8j0bqdd.fsf@gnu.org> (raw)
In-Reply-To: <87r0tsm7u4.fsf@ngyro.com> (Timothy Sample's message of "Mon, 13 Mar 2023 19:37:23 -0600")

Hi Timothy,

Timothy Sample <samplet@ngyro.com> skribis:

> Allow me to present to you a long-overdue update to the Preservation of
> Guix (PoG) report: <https://ngyro.com/pog-reports/2023-03-13/>.  🎉

Yay, thank you!!

Do you think this could be turned into a Guix System service, with an
eye towards making it run on project infrastructure?

> Over the whole set, 77.1% are known to be safely tucked away in the
> Software Heritage archive.  But it’s actually much better than that.  If
> we only look at the most recent sampled commit (from Sunday the 5th),
> that number becomes 87.4%, which is starting to look pretty good!

Truly impressive!

> I have a few more notes on the report, but I want to put this near the
> top of the message so that people will see it.  :)  I wrote a script
> (see attached) that uses the PoG database to find missing sources on a
> packge-by-package basis.  That is, you can run
>
>     guix repl specification-to-swhids.scm pog.db bash

Neat!

>     • Subversion support (for TeX-based documentation stuff, I guess)
>     • bzip2 support for Disarchive (there are 45 bzip2 tarballs)
>     • ZIP support for Disarchive (for the 8 ZIP files)
>     • lzip support for Disarchive (or a workaround for ed)
>     • Fix some issues (gettext is .tar.gz, but something went wrong)
>     • Do something with the static bootstrap binaries

Subversion support should probably be high-priority because TeX Live is
deep down in the dependency graph so if we ever lose it, we’re doomed.

Thanks for the update!

Ludo’.


  parent reply	other threads:[~2023-03-16 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14  1:37 Preservation of Guix (PoG) report 2023-03-13 Timothy Sample
2023-03-14 10:36 ` Simon Tournier
2023-03-18 20:35   ` Timothy Sample
2023-03-22 14:21     ` Ludovic Courtès
2023-03-16 16:41 ` Ludovic Courtès [this message]
2023-03-19  2:25   ` Timothy Sample

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=87v8j0bqdd.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).