From: Timothy Sample <samplet@ngyro.com>
To: guix-devel@gnu.org
Subject: Preservation of Guix 2021-10-22
Date: Fri, 22 Oct 2021 21:09:09 -0400 [thread overview]
Message-ID: <87v91o35u2.fsf@ngyro.com> (raw)
Hey all,
As promised, here is the updated Preservation of Guix Report:
https://ngyro.com/pog-reports/2021-10-22/
It takes into account the as yet unreleased Disarchive fix. The results
are quite a bit better! Note especially that for the most recent
commit, of the 72.8% that I could check, 97.8% are in the SWH archive.
I didn’t add the breakdowns that zimoun suggested (yet), but here is a
bit of extra information. Of the missing fixed-output derivations, we
have:
git 376
tar+gz 3092
total 3468
If we limit ourselves to the most recent commit (258a27e):
git 217
tar+gz 78
total 295
My guess (and that’s all it is!) is that before “sources.json”, a lot of
tarballs slipped through the cracks. Now, most of the tarballs are
getting archived via “sources.json”, but since the Git references are
not, there are several that are being missed.
I was curious about the tarballs in the most recent commit, so I took a
look. There’s no clear pattern. There were three old GNU packages
(from “commencement.scm”), which I thought was strange, because SWH has
a special GNU loader. OK, let’s look at Gawk 3.0.0. It’s there, but
the ID is different. It turns out the SWH version is missing the
executable bit on all the scripts. I wonder if they somehow made a
mistake when they first ingested it.... (At least it’s not *another*
Disarchive bug!)
-- Tim
next reply other threads:[~2021-10-23 1:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 1:09 Timothy Sample [this message]
2021-10-23 7:52 ` Preservation of Guix 2021-10-22 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
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=87v91o35u2.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=guix-devel@gnu.org \
/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).