Matthias Köppe

> The majority of platforms that are listed are themselves not supported anymore; e.g. 20 jobs correspond to Fedora 30 through 40, minimal _and_ standard, all of which are past...

The branches that this creates -- they do not contain the Sage sources, correct?

> how does one see which parts of the diff are _just_ from this particular PR and not from (say) #37810? Actually #37810 is not merged here yet. I prepared...

> I don't know if we want to make it a standard package, is this draft currently adding it as optional? Yes, it's adding it as "optional" (see file `build/pkgs/pygambit/type`)....

The new packaging looks all good, and installing in Sage is already working with the present branch. On our side just the uses of the old `gambit` Python API need...

This looks like a good idea, thanks.

This bypasses DESTDIR staging, which break uninstallation. That's a regression ``` $ cat local/var/lib/sage/installed/nauty-2.8.8.p0 { "package_name": "nauty", "package_version": "2.8.8.p0", "install_date": "Sun Jan 14 09:25:54 PST 2024", "system_uname": "Darwin egret.local 23.2.0...

It also writes into a nonsense directory `local/libdata/pkgconfig/` Oops, my fault I didn't notice this. I've notified the upstream, and I'll patch nauty's makefile.in accordingly.

The CI runs automatically for everyone who has previously contributed to the project. It does not depend on Triage privileges. Approvals of CI runs by Maintainers are only required for...

> You can see CI running on my fork: https://github.com/dimpase/sage/actions/runs/8309020742/job/22739907714 The Build & Test CI doesn't show anything useful for a ticket like this. You need to run the "CI...