From: Timothy Sample <samplet@ngyro.com>
To: "Antoine R. Dumont (@ardumont)" <ardumont@softwareheritage.org>
Cc: Simon TOURNIER <simon.tournier@inserm.fr>,
"swh-devel@inria.fr" <swh-devel@inria.fr>,
"community@nixos.org" <community@nixos.org>,
"guix-devel@gnu.org" <guix-devel@gnu.org>,
"ludovic.courtes" <ludovic.courtes@inria.fr>
Subject: Re: [swh-devel] Call for public review - SWH Nix/GNU Guix stack
Date: Tue, 16 Jan 2024 14:39:52 -0600 [thread overview]
Message-ID: <871qahc8rr.fsf@ngyro.com> (raw)
In-Reply-To: <87o7dnq85z.fsf@gmail.com> (Antoine R. Dumont's message of "Mon, 15 Jan 2024 10:04:40 +0100")
Hello,
This is very exciting work, thanks everyone!
"Antoine R. Dumont (@ardumont)" <ardumont@softwareheritage.org> writes:
> FWIW, in the "new" lister [1] implementation, there are a bunch of extra
> computations done [1] to try and resolve those situations. It's trying
> to fetch more information from upstream server (e.g. crates urls which
> ends in /download, ...) now. It's probably not exhaustive though.
>
> [1] https://gitlab.softwareheritage.org/swh/devel/swh-lister/-/blob/master/swh/lister/nixguix/lister.py?ref_type=heads
I was just looking over some of the new results and noticed that crates
are being treated as ‘content’ rather than ‘tarball-directory’. E.g.:
https://webapp.staging.swh.network/browse/content/sha1_git:e05b33b2d3b40254ceaaa5fe4c501d1b15c75ea6/?origin_url=https://crates.io/api/v1/crates/diff/0.1.12/download
Is that because the changes you describe were done after the staging
data was loaded or is it a bug?
-- Tim
next prev parent reply other threads:[~2024-01-16 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKFPOSwdnSgjtOSW2CbaNyDEivGqan-gJaE_GVrZ7tbj83zRhg@mail.gmail.com>
2024-01-11 12:32 ` [swh-devel] Call for public review - SWH Nix/GNU Guix stack Ludovic Courtès
2024-01-12 18:42 ` Simon TOURNIER
2024-01-15 9:04 ` Antoine R. Dumont (@ardumont)
2024-01-15 11:22 ` Ludovic Courtès
2024-01-16 20:39 ` Timothy Sample [this message]
2024-01-19 16:44 ` Antoine R. Dumont (@ardumont)
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871qahc8rr.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=ardumont@softwareheritage.org \
--cc=community@nixos.org \
--cc=guix-devel@gnu.org \
--cc=ludovic.courtes@inria.fr \
--cc=simon.tournier@inserm.fr \
--cc=swh-devel@inria.fr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.