Whoops. That's an oversight in d/control - it should say python3 instead of python.
This was fixed upstream last year ( https://github.com/apertium/apertium-separable/issues/28), so I was certain this must be a bogus bug report - but no, I plain forgot to adjust d/control. -- Tino Didriksen On Mon, 8 Mar 2021 at 12:39, Matthias Klose <d...@debian.org> wrote: > Package: src:apertium-separable > Version: 0.3.6-1 > Severity: serious > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html > > Your package either build-depends, depends on Python2, or uses Python2 > in the autopkg tests. Please stop using Python2, and fix this issue > by one of the following actions. > > - Convert your Package to Python3. This is the preferred option. In > case you are providing a Python module foo, please consider dropping > the python-foo package, and only build a python3-foo package. Please > don't drop Python2 modules, which still have reverse dependencies, > just document them. > > > At this point, this is the only option. >