Upgrade to givaro-4.2.0 fflas-ffpack-2.5.0 linbox-1.7.0

[ClementPernet]

New packages are available here (with the corresponding checksums):

givaro: https://github.com/linbox-team/givaro/releases/tag/v4.2.0

fflas-ffpack: https://github.com/linbox-team/fflas-ffpack/releases/tag/v2.5.0

linbox: https://github.com/linbox-team/linbox/releases/tag/v1.7.0

The new versions require "a C++ compiler supporting C++11 standard. More precisely g++ v5 or greater, clang++ v3.4 or greater".
So this ticket depends on dropping support for some systems, see #32074.

Depends on #33316

CC: @kiwifb @orlitzky

Component: packages: standard

Branch/Commit: u/cpernet/upgrade_to_givaro_4_2_0_fflas_ffpack_2_5_0_linbox_1_7_0 @ 4006e10

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

[ClementPernet]

Description changed:

--- 
+++ 
@@ -1 +1,5 @@
+New packages are available here (with the corresponding checksums):
 
+givaro: https://github.com/linbox-team/givaro/releases/tag/v4.2.0rc0
+fflas-ffpack: 
+linbox: 

[ClementPernet]

Description changed:

--- 
+++ 
@@ -1,5 +1,7 @@
 New packages are available here (with the corresponding checksums):
 
 givaro: https://github.com/linbox-team/givaro/releases/tag/v4.2.0rc0
+
 fflas-ffpack: 
+
 linbox: 

[mkoeppe]

comment:3

I see numerous build errors in https://github.com/linbox-team/fflas-ffpack/runs/4383290866?check_suite_focus=true that will need fixing before we can do these updates

[ClementPernet]

comment:5

Of course. I just created this ticket to start working on a its branch, which will help us fix the last issues before cutting the final releases.
Btw, I did not manage to access to the full artifact of the givaro install log givaro which caused the failures in these github action builds (only the tail of the givaro-log is displayed in the sage build log in your link). Is there any way to access it? (I could not find it in the whole log archive).

[ClementPernet]

Branch: u/cpernet/upgrade_to_givaro_4_2_0_fflas_ffpack_2_5_0_linbox_1_7_0

[ClementPernet]

Description changed:

--- 
+++ 
@@ -2,6 +2,6 @@
 
 givaro: https://github.com/linbox-team/givaro/releases/tag/v4.2.0rc0
 
-fflas-ffpack: 
+fflas-ffpack: https://github.com/linbox-team/fflas-ffpack/releases/tag/v2.5.0rc1
 
 linbox: 

[ClementPernet]

New commits:

55bd2fa	update to givaro-4.2.0rc0
be8b20d	fflas-ffpack-2.5.0rc1
bd36004	fflas-ffpack-2.5.0rc1 fingerprints

[ClementPernet]

Commit: bd36004

[mkoeppe]

comment:8

Replying to @ClementPernet:

I did not manage to access to the full artifact of the givaro install log givaro which caused the failures in these github action builds (only the tail of the givaro-log is displayed in the sage build log in your link). Is there any way to access it? (I could not find it in the whole log archive).

In each run, such as https://github.com/linbox-team/fflas-ffpack/runs/4383290866?check_suite_focus=true, there is a section "Print out logs for immediate inspection" in the output, which shows all logs of failing package builds in full.

When all jobs have completed, the summary page, such as https://github.com/linbox-team/fflas-ffpack/actions/runs/1526437644, gives access to the log artifacts.
For example, logs-commit-3e42b4a1aaa585bce832738d5a8885dcf7c4273e-tox-docker-ubuntu-xenial-standard (https://github.com/linbox-team/fflas-ffpack/suites/4521078418/artifacts/121757925) gives a zip file within which you will find logs/pkgs/givaro-git.log

[mkoeppe]

comment:9

We have a bit of documentation on this at https://doc.sagemath.org/html/en/developer/portability_testing.html#automatic-parallel-tox-runs-on-github-actions; if you feel anything needs to be added, let me know

[ClementPernet]

comment:10

Thanks a lot for the pointers.