Tobias Diez

> I've no idea what this is supposed to be testing. This is definitely not the way a user would be installing sagemath on void linux, or is it? It's...

You can just `pip install .` as with every other python project. Or use use `meson install`. See https://doc.sagemath.org/html/en/installation/meson.html#background-information for build instructions. (btw, did you saw my previous message above?)

> > > I've no idea what this is supposed to be testing. This is definitely not the way a user would be installing sagemath on void linux, or is...

> @tobiasdiez in your long comment, the `cython` line in `uv pip` instructions is repeated twice. Where exactly do you find this duplication? I made a small mistake while merging...

Right, thanks. In this comment it's indeed still wrong - but it's correct in the branch.

@tornaria In https://github.com/sagemath/sage/pull/40142, I've now added the flag to use system site packages for the venv. Is there anything else I can do to make these CI runs more useful...

> a meaningful use of CI here would be to test if one can _develop_ Sage on void: that is, install the dependencies from the system, and build/test sagelib as...

Reverted back to the glibc version, since github actions run into issues on musl (https://github.com/actions/runner/issues/3852).

okay done at https://github.com/sagemath/sage/issues/40538.

> https://github.com/sagemath/sage/actions/runs/16703101385/job/47277223668#step:11:1 > > shows that gmp (!) does not get built. Why does it even try? This is a known issue, appeared some time ago.