Bug#986527: sagemath: FTBFS: /<<PKGBUILDDIR>>/sage/src/bin/sage: line 549: exec: cython: not found

[Jochen Sprickerhof]

Hi Scott,

* John Scott <jscott at posteo.net> [2021-05-03 00:35]:
>Has anyone been able to reproduce this? Attempting to build Sage in a
>fresh unstable environment succeeds for me; perhaps the build failure
>was spurious.

I triggered reproducible builds yesterday:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sagemath.html

The problem Lucas found is:

* Lucas Nussbaum <lucas at debian.org> [2021-04-07 08:51]:
>> make[4]: Entering directory '/<<PKGBUILDDIR>>'
>> Error: 210 tests failed, up to 200 failures are tolerated
>> make[4]: *** [debian/rules:165: had-few-failures] Error 1

whereas the RB runs above produced:

Success: 41 tests failed, up to 200 failures are tolerated
Success: 5 tests failed, up to 200 failures are tolerated

The 200 is set in debian/rules:

https://salsa.debian.org/science-team/sagemath/-/commit/6088e9f2abc7ae99a8d07760ceee6fb6aac7bb54

and sounds a little arbitrary. Sadly the state upstream seems not to be 
much better:

https://github.com/sagemath/sage/tree/9.2

13 failing, 17 cancelled, and 70 successful checks

(I did not look into them.)

So I think the question is rather if the test suite gives an 
appropriate view on the quality of the software. If it does, I assume 
it is not appropriate for a Debian stable release. Contrary if we assume 
the test suite being broken, we could disable it completely rather then 
producing random FTBFS.

Cheers Jochen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20210504/fd194142/attachment.sig>