[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Disarchive and SHA
From: |
zimoun |
Subject: |
Re: Disarchive and SHA |
Date: |
Thu, 21 Oct 2021 23:22:54 +0200 |
Hi,
On Thu, 21 Oct 2021 at 22:28, Ludovic Courtès <ludo@gnu.org> wrote:
>> That’s why «Disarchive entry refers to non-existent SWH directory».
>
> However, some time ago, the zabbix.com URL was 200-OK, and at that point
> SWH would have ingested it, no?
Timothy pointed [1] then click to «Show all visits».
1:
<https://archive.softwareheritage.org/browse/origin/visits/?origin_url=https://guix.gnu.org/sources.json>
> Or were we unlucky and the URL was already 404 by the time SWH read its
> first ‘sources.json’?
Well, I do not know how to check. Somehow, the ’sources.json’ should
contains the fixed-outputs substitutes in addition to the upstream
content. And probably from both build farms.
It is something I wanted to do but I never took the time to complete
because it was not clear at the time how to compute the hash in
address. Now fixed-output is cleared for me. :-)
>> Help welcome for improving this ’sources.json’. :-) Especially, turning
>> the current way using the website builder into derivation-style usable
>> by the CI.
>
> Yes, it’s probably a good idea to eventually turn ‘sources.json’ into a
> ‘computed-file’, and make a one-element manifest under etc/.
It is not clear how to deal with packages into a ’computed-file’. For
instance, etc/disarchive-manifest.scm create one store item per package
(somehow) then build a directory union. Here the union is a file.
Well, it is not clear for me how to process.
Cheers,
simon