Refs. swh/infra/sysadm-environment#5183

Refs. swh/infra/sysadm-environment#5110

Refs. swh/infra/sysadm-environment#5110

Refs. swh/infra/sysadm-environment#5211

Refs. swh/infra/sysadm-environment#5110

according to latest migrations as most were outdated.

Refs. swh/infra/sysadm-environment#5205

This reverts commit ef66ebd3.

Most were outdated.

Refs. swh/infra/sysadm-environment#5205

Related to swh/infra/sysadm-environment#5199

This reverts commit b358c3d2. This
update is not ready yet. Quoting pabs:

> […] I noticed that resubmitting a forge using the same URL and a
> different forge type is blocked with Request for forge already exists
> (id 240) when the forge was already added via Add Forge Now. So this MR
> will need to wait for a fix for that issue, or the process for
> submitting forge updates will need to be rethought.

Asked-in: https://archive.softwareheritage.org/admin/add-forge/request/155/

This is now used (esp. by swh-alter but it should be generalized) to
process svg images for publication.

it's not ready to be published.

Distribute these Makefiles in share/swh-docs and move the
glossary.rst in share/swh-docs/docs/devel to keep the directory hierarchy
of the source repo.

Distribute this docs/devel/glossary.rst file as package data in
share/swh-docs since it is needed for locally building the doc
from swh packages.

Adapt the add_glossary_to_index sphinx hook to look for this file in
share/swh-docs in addition to the current relative path (which only
works if swh-docs in installed in editable with proper pip
config-settings and who knows what else). For local/editable installed
swh-docs, look a bit more than previously to attempt to catch the case
of editable_mode=strict pip config

This is the inventory we need in order to resolve swh/meta#4931

The idea is to generalize the fact that all the swh packages should have
a README file in the root directory, but this should be included in the
sphinx documentation, for which the simplest way is to make the file
symlinked in docs/. For several reasons, it's simpler to make this
symlink creation handled by a hook/automation script at doc build time
rather than add the symlink in the git repo of the swh package.

Some extensions we are using does not declare them as safe for parallel read
so sphinx emits warnings when parallel build is used.

Filter out these warnings to fix CI builds.

It should fix doc CI builds as parallel build was recently enabled in jobs.

Antoine Lambert authored 2 years ago and Antoine Lambert committed 1 year ago

It was excluded a couple of years ago as no relevant Python code was
contained in that package but this is no longer the case.

Those URLs makes the ShortenLinkTransform sphinx post-transform from the
pydata theme raise an exception when it attempts to process them using
Python >= 3.11.4, see https://github.com/python/cpython/issues/103848.

So align with other service URLs containing brackets in that doc page
and remove their scheme.

Latest pydata-sphinx-theme release prints a new warning about
an accessibility issue and recommends to set to False the
navigation_with_keys theme option.

It fixes CI jobs on Jenkins as sphinx warnings are treated as
errors.

See https://github.com/pydata/pydata-sphinx-theme/issues/1492

Paul Wise authored 1 year ago and Jérémy Bobbio (Lunar) committed 1 year ago

Asked-in: https://archive.softwareheritage.org/admin/add-forge/request/200/