Bug#942106: looking at the remaining "bad" packages in the "add python 3.8" transition

2020-01-18 Thread Julien Puydt
Le dimanche 19 janvier 2020 à 00:54 +, peter green a écrit : > > There's another kind of issue > Yeah, sadly the transition tracker only looks at unstable, so > packages that are fixed in unstable but haven't migrated to testing > for some reason won't show up. > > ; here is an example : > >

Bug#942106: looking at the remaining "bad" packages in the "add python 3.8" transition

2020-01-18 Thread peter green
There's another kind of issue Yeah, sadly the transition tracker only looks at unstable, so packages that are fixed in unstable but haven't migrated to testing for some reason won't show up. ; here is an example : - sagemath builds only for Python 3.7, so some of this subpackages don't load

Bug#942106: looking at the remaining "bad" packages in the "add python 3.8" transition

2020-01-18 Thread Julien Puydt
Le samedi 18 janvier 2020 à 02:38 +, peter green a écrit : > I just took a look at the "add python3.8 transition tracker", and > split the remaining "bad" packages into categories. There's another kind of issue ; here is an example : - sagemath builds only for Python 3.7, so some of this

Bug#942106: looking at the remaining "bad" packages in the "add python 3.8" transition

2020-01-17 Thread peter green
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