Hello, On 03/01/2019 07:20, Thorsten Glaser wrote: > Hi Jerome, > >> The issue was resolved in package 0.4.1+ds-2. > > you “resolved” it by no longer building the binary package. > > However, there are packages still (build-)depending on it, > which you might wish to inform: see #918079 for an example, > > You might also with to file an RM (RoM) bug with ftpmasters > so that they remove the stray binary package from the archive; > the current situation has it still available, making quinn-diff > believe that its r-build-depends are installable, whereas the > package fails to configure. This is bad. > > If not all users can switch to python3-nbsphinx in time for > the release, it might make sense to package python-nbsphinx > 0.3.x separately, like it was done with src:matplotlib2, for > the packages still depending on the Python 2 version. (It is > intended, after all, that Python 2 support will be kept until > some time after buster, but before bullseye, after all.)
My understanding is that sphinx no more support Python as well (this is the excuse from the uptream maintainer): if sphinx still supports Python 2 in Buster, then it makes sense to make nbsphin supporting Python 2 in Buster. Ok, I will have a look this week end. Cheers, Jerome > > Thanks, > //mirabilos > -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B
signature.asc
Description: OpenPGP digital signature
