For the rpm support, [1] may help.

Heads up, it seems the main issues mentioned above have subsided.
It's still ongoing but the tendency seem to go the right way.

@anlambert fixed plenty of issues including some from this ticket (thanks a bunch).

I'm planning on deploying those changes soon (around noon, i'm on something else currently).

And i'll trigger another run on staging after that ;)

@anlambert fixed plenty of issues including some from this ticket (thanks a bunch).

P1158 and P1159 with some updated errors from the last run.

I'll udpate those tomorrow as it's still ongoing.

In T3468#70305, @ardumont wrote:

P1158 and P1159 with some updated errors from the last run.

P1158 and P1159 with some updated errors from the last run.

I'll trigger a new run of loading the opam origins in staging so the dataset of issues is updated.

For the rpm support, [1] may help.

Done and a full run got done.

Expectedly, there are errors but that's outside the scope of the deployment. Those can
be browsed in the associated dashboard [2] and filtering by priority = 3 to eventually
chase and fix.

Heads up on this, both opam lister and loader have been deployed on the staging infra.
More details on the dedicated task [1].

I forgot to upgrade the swh.loader.core package which is actually holding the new package loader...

I may have missed something though, investigating what exactly.

Scheduling those origins [1] for the loading went less well [2]
I may have missed something though, investigating what exactly.

Listing execution went well [1]. New listed origins stored in the scheduler as expected
[2].