New comment by tornaria on void-packages repository

https://github.com/void-linux/void-packages/pull/44160#issuecomment-1567673646

Comment:
@dkwo: maybe you want to test; still WIP.

I've been insistent on making check pass as much as possible.  Yet there are some circular checkdepends (but not that many) so CI might fail... we'll see.

Cycles I know about:
 - `jupyter_client`, `ipython` have `checkdepends` on `ipykernel`, but the latter build depends on the former
 - `ipython` has `checkdepends` on `nbformat`, but the latter build depends on the former
 - `ipykernel` has `checkdepends` on `ipyparallel`, but the latter build depends on the former
 - `nbclient` has `checkdepends` on `nbconvert`, but the latter build depends on the former
 - `jupyter_server_terminals` has `checkdepends` on `jupyter_server`, but the latter build depends on the former
 - `pytest_jupyter` has `checkdepends` on `jupyter_server`, but the latter check depends on the former

There are no build cycles.

I guess CI cycles can be broken by setting `make_check=ci-skip` in a few packages. In principle this is only a problem if two packages are updated in the same PR (like here, everything is updated at the same time since lots of packages are quite old).