From: Antoine Lambert <antoine.lambert@inria.fr>
To: swh-devel@inria.fr, "Ludovic Courtès" <ludovic.courtes@inria.fr>
Subject: bug#69070: [swh-devel] No releases/revisions in /snapshot endpoints?
Date: Mon, 12 Feb 2024 17:37:22 +0100 [thread overview]
Message-ID: <f11611f7-9f37-42b1-8e58-726d8223ffb0@inria.fr> (raw)
In-Reply-To: <87il2td5yc.fsf@gnu.org>
Hello Ludovic,
The SWH data model also allows for snapshot branches to target simple directories.
The new loaders we implemented to ingest a tarball content (visit type: tarball-directory)
or a directory targeted by a CVS tag or commit (visit types: git-checkout, hg-checkout)
produce such snapshot with a single non alias branch targeting a directory.
We do not produce revisions or releases with these loaders as their purpose is to
archive a single directory (with extid mapping) without any development history.
Antoine Lambert
On 12/02/2024 17:04, Ludovic Courtès wrote:
> Dear SWH,
>
> In <https://issues.guix.gnu.org/69070> I stumbled upon what might be new
> behavior from the /snapshot endpoint:
>
>> The crux of the problem is that ‘snapshot-branches’ used to return
>> either a “revision” or a “release”, but now it can also return a
>> “directory”:
>>
>> $ wget -qO- https://archive.softwareheritage.org/api/1/snapshot/c405490b80fb35cc58b34260d9ec6add8248857f |jq
>> {
>> "id": "c405490b80fb35cc58b34260d9ec6add8248857f",
>> "branches": {
>> "1.3.2": {
>> "target": "e4a4be18fae8d9c6528abff3bc9088feb19a76c7",
>> "target_type": "directory",
>> "target_url": "https://archive.softwareheritage.org/api/1/directory/e4a4be18fae8d9c6528abff3bc9088feb19a76c7/"
>> },
>> "HEAD": {
>> "target": "1.3.2",
>> "target_type": "alias",
>> "target_url": "https://archive.softwareheritage.org/api/1/directory/e4a4be18fae8d9c6528abff3bc9088feb19a76c7/"
>> }
>> },
>> "next_branch": null
>> }
> Current documentation mentions the ‘target_types’ query parameter, which
> I could use to restrict results to “revision” and “release”:
>
> https://archive.softwareheritage.org/api/1/snapshot/doc/
>
> However, that’d be the empty list of the case above.
>
> Other snapshots seem to be missing releases and revisions as well, such
> as this one:
>
> https://archive.softwareheritage.org/api/1/snapshot/55bda9214f962550baad25026fb3ac3ad12e3eb9/
>
> Did anything change here? Am I holding it wrong? :-)
>
> Thanks in advance,
> Ludo’.
--
Antoine Lambert
Software engineer for Software Heritage
https://www.softwareheritage.org
Inria, Paris
prev parent reply other threads:[~2024-02-24 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 10:11 bug#69070: ‘guix lint -c archival python-scikit-learn’ crashes Ludovic Courtès
2024-02-12 16:04 ` bug#69070: No releases/revisions in /snapshot endpoints? Ludovic Courtès
2024-02-12 16:37 ` Antoine Lambert [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=f11611f7-9f37-42b1-8e58-726d8223ffb0@inria.fr \
--to=antoine.lambert@inria.fr \
--cc=ludovic.courtes@inria.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 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).