Bug#929954: Status of this issue WRT freeze

2019-07-24 Thread Elena ``of Valhalla''
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

Bug#929954: Status of this issue WRT freeze

2019-07-22 Thread Sebastiaan Couwenberg
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

Bug#929954: Status of this issue WRT freeze

2019-06-07 Thread Matthias Klose
On 07.06.19 09:21, Elena ``of Valhalla'' wrote: > Hello > > I've given a look at the code, and I expect that what happened is an > implicit import that changed inside reportlab, but I agree that the > right place to fix this is in rst2pdf. > > Since we are in freeze, however, I'd like to know

Bug#929954: Status of this issue WRT freeze

2019-06-07 Thread Elena ``of Valhalla''
Hello I've given a look at the code, and I expect that what happened is an implicit import that changed inside reportlab, but I agree that the right place to fix this is in rst2pdf. Since we are in freeze, however, I'd like to know whether the changed reportlab is meant to enter buster or not: I