Re: Preservation of Guix report for 2024-01-26

2024-02-06 Thread Ludovic Courtès
Hello! Timothy Sample skribis: > I sent https://issues.guix.gnu.org/68769. Now I see that I didn’t have > the newest Git hooks installed, so no change ID and no email to the > relevant team. Sorry! (I use worktrees so the Makefile didn’t fix this > for me automatically – I should have double

Re: Preservation of Guix report for 2024-01-26

2024-01-30 Thread Timothy Sample
Ludovic Courtès writes: > Thumbs up on bzip2 support! We should update Disarchive in Guix but > perhaps that’s already in your pipeline? I sent https://issues.guix.gnu.org/68769. Now I see that I didn’t have the newest Git hooks installed, so no change ID and no email to the relevant team. So

Re: Preservation of Guix report for 2024-01-26

2024-01-29 Thread Ludovic Courtès
Hi Timothy! Timothy Sample skribis: > The permalink is https://ngyro.com/pog-reports/2024-01-26, but you can > link to the latest report, too: https://ngyro.com/pog-reports/latest/. Yay! > New in this edition is checking for Subversion sources and > bzip2-compressed tarballs. Subversion is we

Preservation of Guix report for 2024-01-26

2024-01-27 Thread Timothy Sample
Hello all, For a while now, I’ve been tracking coverage of Guix sources in the Software Heritage (SWH) archive. I maintain a dataset of sources that goes back (almost five years) to Guix 1.0.0. Every once in a while, I update this dataset and check it against SWH to see how much is missing. I ju