Comment 2 for bug 1980854

Hi pd9370, thanks for reporting this.

I know little about Devuan (besides the tagline), but I assume that tox is not actually used during the package build process, right? On Ubuntu/Debian, I think sbuild just invokes a python3 -m pytest -v tests/unittests with system dependencies. The failing test exists in tox to verify the oldest supported distro dependency versions (using our CI infrastructure or locally with pyenv/deadsnakes/etc).

Agreed, the issues you described may be worked around on newer versions, but the intended use case currently is running on 3.6 so I'm not sure working around this issue on other versions really makes sense - what does it buy us? For what it's worth, that test env fails when executed with system-provided python on the latest Ubuntu release (Jammy).

It might make sense to drop that environment from the tox envlist to reduce noise.

Thoughts?