tox.ini: debian-bullseye, -sid have Python3.8 instead of 3.7

[cduston44]

As per the wiki, running

build/bin/write-dockerfile.sh debian "@(standard|optional)" > Dockerfile

Generates a Dockerfile, but running the dockerfile fails because Debian (at least) comes with Python3.8, not 3.7. This can be fixed by changing the file build/pkgs/python3/distros/debian.txt, but I don't know if that will have unexpected consequences.

CC: @dimpase @kliem

Component: porting

Author: Matthias Koeppe

Branch/Commit: 1e7becc

Reviewer: Jonathan Kliem

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

[mkoeppe]

comment:1

Yes, this will have to be changed when we support Python 3.8 (#27754). At the moment, we only accept Python 3.7.x in configure; ticket #29033 adds Python 3.6.x support.

[mkoeppe]

comment:2

Also, see the flag IGNORE_MISSING_SYSTEM_PACKAGES in tox.ini, which we use both for too old versions of the distribution that don't have all packages, and for too new versions of the distribution, such as ubuntu-focal.

[mkoeppe]

Branch: u/mkoeppe/tox_ini__debian_bullseye___sid_have_python3_8_instead_of_3_7

[mkoeppe]

Commit: 1e7becc

[mkoeppe]

New commits:

1e7becc

tox.ini [debian-buster, -sid]: IGNORE_MISSING_SYSTEM_PACKAGES=yes because of libpython3.7-dev

[mkoeppe]

Author: Matthias Koeppe

[kliem]

Reviewer: Jonathan Kliem

[kliem]

comment:7

I already noticed the problem. So what this does it just make the workflow go through, even though it coulnd't install python3.7. It will later find out that no suitable python can be found and install python3.7 for sage.

[mkoeppe]

comment:8

That's right. Best we can do before we get to Python 3.8 compatibility in #27754, which seems to have stalled

[mkoeppe]

comment:10

Thanks!

[vbraun]

Changed branch from u/mkoeppe/tox_ini__debian_bullseye___sid_have_python3_8_instead_of_3_7 to 1e7becc