Remains a bunch of services not existing yet in the elastic stack (vault cooker, deposit checkers and indexer journal clients).
So the plan would be to integrate those in the elastic stack.

• nixguix: Keep only one url as origin and other urls as fallback ones

Align file tarball listing on what we do for tarballs.

Hum, for the 7 false, I have to check. For the 88 packages with no-origin, it is more
annoying. Well, some are metapackages as gcc-toolchain, so they can be skipped. Is it
ok for you to let this 'no-origin' type? For some others, I have to check if they are
covered elsewhere.

For ^, something like this would do [1]

• nixguix: Keep only one tarball origin sending along fallback urls

Thanks for all that ^! And great pointers!

I've moved around the parent task as the lister should be able to do something about this.

This perimeter enters the scope of T3781.

I either remembered an old stateless implementation or i remember another
implementation altogether.

I'll unstuck the situation by resetting that state.

But on my side, the "stateless" lister starts from the problematic page (17), and then
plainly stops... [2].

Note that there is a misbehavior in terms here for that "stateless" typed lister. If it
is indeed a stateless lister, it should start from scratch each time it runs. If it has
an incremental behavior (it seems so from that described behavior) then it should be
probably typed differently.

ah i think i got it...

As a shot in the dark, i've changed the list task arguments [1] but i'd be surprised if that'd change anything...

I noticed your remarks but that's not what's happening in staging [3] for some unknown reason [1]

ok, thanks, it's clearer.

I got some questions and suggestions inline.

I'm not so sure in real life, 500 -> 500 -> 200 will happen that much often but let's see.