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 <guix-devel@gnu.org>, zimoun <zimon.toutoune@gmail.com>
Subject: Re: ImageMagick from 2020?
Date: Mon, 24 Jan 2022 16:00:25 +0100	[thread overview]
Message-ID: <87a6fltbzq.fsf@gnu.org> (raw)
In-Reply-To: <87pmoj7m3y.fsf@ngyro.com> (Timothy Sample's message of "Sat, 22 Jan 2022 11:48:17 -0500")

Hi!

Timothy Sample <samplet@ngyro.com> skribis:

> I also played around with it and came up with
>
>     https://ngyro.com/pog-reports/2022-01-16/missing-sources.json
>
> This is a “sources.json” that only lists the “missing” and “unknown”
> sources from the PoG report.  It lists sources across all commits (since
> 1.0.0).  This might be the easiest thing for SWH to handle, since it
> omits nearly 20k sources that they definitely already have.  Since they
> don’t have the tarball hashes, they have no way to skip downloading and
> processing tarballs that they already have by hash.  Hence, filtering it
> with the extra data we have through the PoG projects should be something
> that they welcome!
>
> If they want, they could point a loader task at
>
>    https://ngyro.com/pog-reports/latest/missing-sources.json
>
> and I could publish updates when I publish new PoG reports.

Sounds great!  Could you ask them whether they could do that?  It may be
that it’s going to be a one-time thing, if everything goes well.

> There’s one other thing to think about.  Some of our sources are
> arguably unsuitable for SWH.  For instance, our bootstrap binaries.  I
> bet we have a bunch of other borderline things, too, like game assets.
> Of course, if they are indiscriminately ingesting Github, I’m sure
> they’ve loaded plenty of garbage.  Mostly, I think about these things
> because I believe it’s important to maintain the Guix-SWH relationship.

Right, it would be nice to filter them out somehow, even though it’s a
drop in the ocean of binaries that SWH ingests routinely (for instance
that’s the reason why we find some tarballs, as is, via
‘lookup-content’).

Thanks,
Ludo’.


      reply	other threads:[~2022-01-24 15:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 17:20 ImageMagick from 2020? zimoun
2022-01-10 18:01 ` Timothy Sample
2022-01-10 18:36   ` Maxime Devos
2022-01-10 18:59     ` zimoun
2022-01-18 14:38     ` Ludovic Courtès
2022-01-18 14:49       ` zimoun
2022-01-19 10:36         ` Ludovic Courtès
2022-01-19 11:30           ` zimoun
2022-01-22 16:48             ` Timothy Sample
2022-01-24 15:00               ` 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

  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=87a6fltbzq.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=samplet@ngyro.com \
    --cc=zimon.toutoune@gmail.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).