On 2019-07-22 at 21:12:34 +0200, Sebastiaan Couwenberg wrote: > Hi Elena, > > On Fri, 7 Jun 2019 09:21:22 +0200 Elena ``of Valhalla'' wrote: > > Of course after the release the severity can be raised back, as then it > > would apply to the majority of users indeed (but I'd just upload the > > new version of the package and be done with it). > > With the buster release and severity increase behind us, now would be a > good time to upload the new version. > > Anything preventing you from doing that?
only the fact that the new version has quite a few changes, is not currently building correctly, and while I have worked on it I haven't had time to finish fixing everything that needed fixing. I have pushed the commits I was sure about, but I still have some uncommitted changes I was trying, so please if you decide to help let me know and we can cohordinate. Also, I'm wondering if it is worth doing this work when the package is at risk of being dropped anyway with the removal of py2 (not immediately, since it has reverse-(build-)dependencies, but probably before the bullseye release). (See also #826908) -- Elena ``of Valhalla''
