I just took a look at the "add python3.8 transition tracker", and split the remaining 
"bad" packages into categories.

Key package, rc bug with patch.
* gpgme1.0 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944774

Not key package, but not marked for autoremoval from testing
* macs version in unstable FTBFS on most architectures, version in testing 
seems to build fine
  with 3.8 according to reproducible builds, but afaict binnmus are not 
currently possible in testing

Builds only against default python3 version
* libcap-ng https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943627
* fontforge https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948016
* pcp can't find a bug report for this one.
* getfem++ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948016
* uhd https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943636
* stimfit https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948020

Marked for autoremoval from testing
* subvertpy https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942678
* beancount https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943608
* python-thinc https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947111

Not in testing (and not mentioned already)
* libyang build timesouts on mipsel/mips64el , probablly heavy swap use
* python-tesserocr https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943501
* pyfai https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945411
* veusz https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945467

Reply via email to