INFO: pip is looking at multiple versions of
sphinxcontrib-serializinghtml to determine which version is
compatible with other requirements. This could take a while.
ERROR: Could not find a version that satisfies the requirement
Sphinx>=5 (from sphinxcontrib-serializinghtml) (from versions: none)
ERROR: No matching distribution found for Sphinx>=5
INFO: pip is looking at multiple versions of sphinxcontrib-jquery to
determine which version is compatible with other requirements.
This could take a while.
ERROR: Could not find a version that satisfies the requirement
Sphinx>=1.8 (from sphinxcontrib-jquery) (from versions: none)
ERROR: No matching distribution found for Sphinx>=1.8
neither firefox nor epiphany can download them, and they are not
well maintained, because rarely tested.
This is WIP because the "(HTTP)" part of "Download (HTTP)" will
need to be removed too.
But let's see what users think first...
It's optional for the packages that use it, and they only use it to
provide additional support for profiling.
Sysprof now requires two more packages which are specific to it, so
let's archive it.
We were saying "-jN means using N cores (or N threads)". This is
completely wrong. "-jN" only tells the building system to run N jobs
simultaneously, but each job can start their own subprocesses or threads
and there is no way for the building system to know how many
subprocesses or threads a job will start.
This caused a lot of misunderstandings and encouraged users to wrongly
blame building systems.
Fix the description of -jN, and add how to use cgroup to control the
usage of CPU cores and system RAM.
On a systemd-based system, systemd is the cgroup manager and manually
operating on cgroups may puzzle systemd. So use systemd-run for
creating and setting up cgroup. On a sysv-based system create and set
up the cgroup manually.
The name of the package in the install command was inadvertently
changed to dbusmock. But this name is unknown to the build system,
and should be python-dbusmock (or python_dbusmock).
