On Sat, Mar 07, 2020 at 07:50:37AM +0100, olivier sallou wrote: > > I cannot reproduce this bug when building inside a clean schroot > > (unstable). I don't know if the reason is because I don't have > > python3.7 installed in the schroot anymore (it was removed recently, and > > python3.8 is the default), or because there's something else different.
Works for me know. > I pushed in february during our sprint some updates in git fixing the > issue. However it implied lots of modification that may impact software as > it implied to do some choices on types (bytes vs str for example with c > binding), without really knowing the impact.... > > We may push the package but other packages using might be broken.... > On other side, package will be removed. > > So either we push an update, knowing that it may not be fully fonctional, > or let it go..... I decided to upload and add a debian/NEWS. I'll ask a future GSoC student to add an extensive autopkgtest (if you will not beat the student since you seem to know more about the package). Kind regards Andreas. -- http://fam-tille.de