Would removing your 3rd requirement (per-package indexes) simplify things? I don't see that as a goal at all, just what happens by default with the minimalistic sphinx setup we used back in the days. I'd be much happier if we could have a single index / navigation bar, where the doc of all modules appear.

Thanks for filing this @moranegg !

The simplest solution would be to check if the computed timezone offset lies in the adequate bounds [UTC−14:00, UTC+14:00] and set it to 0 if not.

@ftigeot thanks for checking!
Please file tasks for changing the failing batteries (priority high) and automate the monitoring of failing batteries so that in the future we will be automatically notified of future similar failures (priority normal).

@anlambert: let's do this. Green light, go ahead!

In T1219#24586, @vlorentz wrote:

Resolved by D622.

thanks! can you ping me when this fix (T1304) is deployed?

thanks! can you ping me when this fix (T1303) is deployed?

Oh, silly me, I commented without checking that first.
Fine by me then :) Thanks!

I've tried this before too, but we can't do that yet, because the version of msgpack we use in Debian stable doesn't yet have raw=False.

In T1304#24431, @anlambert wrote:

This seems due to releases pointing to missing revisions in the archive, see for instance http://localhost:5004/api/1/release/21d03ad29cfa315d8b7e5d7577964fbc21797f74/

In T1249#24433, @douardda wrote:

I suggest to call it good as is, and set a proper solution up if and only if it really obviously cause problems...

(I also note that the search results page treat both cases similarly: showing an X for both kind of origins. Good!)

To elaborate, the user-visible result should be the same of origins that haven't been visited yet, e.g.:

In D592#11583, @olasd wrote:

I don't quite understand what the "fs" marks are supposed to convey, but they're carried over from nose without change, so *shrug*.

To try this i've re-installed locally swh-core and got the swh-db-init entry point. However, it fails as follows:

$ swh-db-init 
Traceback (most recent call last):
  File "/home/zack/.local/bin/swh-db-init", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3105, in <module>
    @_call_aside
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3089, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3118, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 578, in _build_master
    ws.require(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 895, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 781, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'msgpack-python' distribution was not found and is required by swh.core

even if I have msgpack installed (it loads fine in ipython3 and i can successfully run all swh-core tests).

abandoning, as raw=False isn't yet part of debian stable version of msgpack

use .[testing] in tox.ini

the internship topic on this is now available here: https://wiki.softwareheritage.org/wiki/Ingest_all_Debian_derivatives_(internship)

add N2T resolution

In D537#10786, @moranegg wrote:

The last comment was submitted rapidly, sorry..

In T1262#23681, @olasd wrote:

Automating the addition of distributions from the Debian derivatives census to Software Heritage would probably be a good topic for an internship, e.g. a Google Summer of Code/Outreachy project.

I'll add n2t.net and resubmit this. Thanks @moranegg

\o/

(i've retitled this according to consensus)