Add more void packages to distros/void.txt

[tornaria]

• The first commit includes all standard packages that can be currently used from system, as well as linbox and maxima which have standing tickets to add (spkg-configure.m4 for linbox #29631 and spkg-configure.m4 for maxima #32867 respectively)

• The second commit includes all python packages that can be used from system after configure --enable-system-site-packages via spkg-configure.m4 for cvxopt and other python packages #29665

• the remaining commits include additional packages that may be useful in the future.

CC: @orlitzky

Component: distribution

Author: Gonzalo Tornaría

Branch/Commit: c44fe9b

Reviewer: Matthias Koeppe

Issue created by migration from https://trac.sagemath.org/ticket/33098

[tornaria]

Author: Gonzalo Tornaría

[tornaria]

Branch: u/tornaria/void-packages

[tornaria]

Commit: 7f5f2ff

[tornaria]

New commits:

a3b730b	void linux: packages that can be used from system
986b7c6	void linux: add python3 packages for #29665
d267273	void linux: more standard python3 packages
6804df2	void linux: more optional python3 packages
7f5f2ff	void linux: add more optional and experimental packages

[orlitzky]

comment:2

Do we have a github (tox) job for Void yet? I'm happy to rubber-stamp this for you if there's no risk of it breaking the CI.

[tornaria]

comment:3

Replying to @orlitzky:

Do we have a github (tox) job for Void yet? I'm happy to rubber-stamp this for you if there's no risk of it breaking the CI.

I haven't paid much attention to tox yet, but there is #33084 and I'll try to look at that. My template for building sage on void knows which dependencies to install so it's not like we need it; this is more to help someone wanting to build from source on void so the suggestion on which packages to install is correct and complete.

We have void-linux/void-packages#34030 which is building and testing sage; it is using all the packages I added in the first commit (including linbox and maxima via patches taken from #29631 and #32867)

All tests pass in our standard architectures (x86_64, x86_64-musl and i686) using all possible system packages with system python 3.10 (using #30766) and assorted patches needed for doctests to pass (right now github shows a failure on i686 but that's just the timeout reported in #33091; I added a patch to solve that but I didn't push yet to gh).

Of the remaining tickets, only the second one should have any effect and only after patching with #29665 (which is my next goal as I want to try to ship sage 9.5 for void using system packages as much as possible).

Anyway, I don't really know how tox uses these package lists, so I may be missing something...

[tornaria]

comment:4

I already found at least one error while trying #29665 (python3-ipython_ipywidgets should be python3-jupyter_ipywidgets).

Let's hold this until I finish testing #29665.

[sagetrac-git]

Changed commit from 7f5f2ff to c44fe9b

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:

cf12322	void linux: add python3 packages for #29665
90e1be7	void linux: more standard python3 packages
5d8c6a0	void linux: more optional python3 packages
c44fe9b	void linux: add more optional and experimental packages