all messages for Guix-related lists mirrored at yhetil.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-11-30
Date: Mon, 06 Dec 2021 14:09:06 +0100	[thread overview]
Message-ID: <87lf0xnaml.fsf@gnu.org> (raw)
In-Reply-To: <87k0gogo0a.fsf@ngyro.com> (Timothy Sample's message of "Wed, 01 Dec 2021 13:48:21 -0500")

Hi!

Timothy Sample <samplet@ngyro.com> skribis:

> Here’s a new version of the Preservation of Guix Report:
>
>     <https://ngyro.com/pog-reports/2021-11-30/>

The PoG reports are all 404 right now.

> Here’s what I wrote:
>
>>  This version has a breakdown by different origin types.  The good
>>  news is that Git origins are doing very well.  We’ve confirmed that
>>  97.2% of the 9,272 Git origins that we’re tracking are in the SWH
>>  archive.  Most of the progress there is due to zimoun wading through
>>  the missing packages and telling SWH to store them – thanks, zimoun!

Yay!

> That’s still basically true this month, but we have a few more missing
> Git sources.  Actually, we are starting to lose sources!  If you look at
> the graph of commits, you can see a sharp increase in missing sources
> for recent commits.  It looks like a problem on the SWH side.  Visiting
> [1] and selecting “Show all visits”, you can see that the nixguix loader
> has been having trouble loading our “sources.json” recently.
>
> [1] <https://archive.softwareheritage.org/browse/origin/visits/?origin_url=https://guix.gnu.org/sources.json>
>
> I will try and get in touch with SWH about this.  While it’s troubling,
> it certainly is a good confirmation that doing some basic monitoring is
> important!

Yup.

> That’s the bad news.  The good news is I’ve added support for XZ to
> Disarchive (to be officially released in Disarchive soon).  That means
> that we have information about 4K more sources.  We now know the status
> of 80% of our sources.  Unfortunately, 40% of the XZ sources are
> missing!  Most of them are old, as can be seen in this (secret) graph:
>
>     <https://ngyro.com/pog-reports/2021-11-30/tar-xz-rel-hist.svg>
>
> (The filename format is “{tar-gz,tar-xz,git}-{rel,abs}-hist.svg” if you
> want to see all the secret graphs.)

Can’t wait to see the secret graphs.  :-)

Thanks!

Ludo’.


      parent reply	other threads:[~2021-12-06 13:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 18:48 Preservation of Guix Report 2021-11-30 Timothy Sample
2021-12-02 14:09 ` Timothy Sample
2021-12-02 17:15 ` zimoun
2021-12-03 10:02   ` Ricardo Wurmus
2021-12-03 13:22     ` zimoun
2021-12-06 13:10   ` Ludovic Courtès
2021-12-06 14:00     ` zimoun
2021-12-06 13:09 ` Ludovic Courtès [this message]

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=87lf0xnaml.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 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.