[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Preservation of Guix Report
From: |
zimoun |
Subject: |
Re: Preservation of Guix Report |
Date: |
Fri, 22 Oct 2021 09:58:14 +0200 |
Hi Timothy,
On Thu, 21 Oct 2021 at 12:26, Timothy Sample <samplet@ngyro.com> wrote:
> Fixing this in Disarchive is going to make a *huge* difference, so that
> is now high priority for me (it’s a one line change, but I want to fix
> it, release it, update Guix, and recompute the report).
Cool! Excited to get the new report.
> Thanks! While investigating the above problem, I found a page that
> lists what SWH is getting from us [1] and another showing when they are
> scanning “sources.json” [2]. I don’t know if you’ve seen them before,
> but they will be invaluable for figuring this stuff out.
>
> [1]
> https://archive.softwareheritage.org/browse/origin/branches/?origin_url=https://guix.gnu.org/sources.json
> [2]
> https://archive.softwareheritage.org/browse/origin/visits/?origin_url=https://guix.gnu.org/sources.json
I do not know these. However, I am confused how to use them. For
instance, clicking to a random orange link:
<https://archive.softwareheritage.org/browse/origin/directory/?origin_url=https://guix.gnu.org/sources.json×tamp=2021-04-27T16:01:28Z>
which points to a snapshot of the Git repo of Guix. I would be
interesting to know what does it mean “partial”. And read the log.
Well, let roam on #swh-devel. ;-)
Cheers,
simon