Sorry for not mailing that to you too. There's a mistune0 package that will allow you to fix that bug, while I'll upload soon an update of python3-mistune.
See the forwarded message below. Pierre-Elliott Bécue <p...@debian.org> wrote on 24/02/2022 at 22:04:28+0100: > [[PGP Signed Part:Good signature from 29BFA0D079290ACA Pierre-Elliott Bécue > <be...@crans.org> (trust ultimate) created at 2022-02-24T22:36:30+0100 using > RSA]] > Hi, > > Following up some exchanges, we agreed within the Python Team to > reupload mistune 0.8.4 under the mistune0 source package. As it passed > NEW, I'm currently doing a sourceful upload and replacing any occurence > of mistune in this package by mistune0. > > Therefore, in 15 days, I'll make all these bugs RC, in order to be able > to update src:mistune to mistune v2 no later than the end of March. > > To rely on python3-mistune0, add it as a dependency of your package, and > make a Debian patch to replace any occurrence of a mistune import or > usage to mistune0. > > This is not ideal, but I guess upstreams will make themselves compatible > with mistune v2 in some future and you'll be able to drop such patches. > > In the meantime, this avoids conflicts between mistune 0.8.4 and 2.0.0 > as both can be installed, and this also allows for things depending on > mistune v2 to enter testing. > > With best regards,
signature.asc
Description: PGP signature
-- PEB
signature.asc
Description: PGP signature
