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 whether the changed > reportlab is meant to enter buster or not: I suspect not, since it is a > new upstream release and I couldn't find any unblock bug.
no, these are all bug fix releases, unfortunately with a clean up for that kind of code ... > > If that is the case, I'd prefer not to do any upload in sid until the > buster release, yes, and remove the buster tag from the report. > but I would do as follows: > > * lower the severity to important, since the package is still usable for > the majority of users (those on buster) (unless it can be tagged as > buster-ignore or there is another way to prevent it from being removing the buster tag should be good enough? > autoremoved from testing, where the package is working); > * check that this issue is still present in the latest upstream version > of the package and in that case forward it upstream; > * on a lower priority, upload the new upstream version to experimental, > if needed with a patch for this issue. > > 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). > > Any objection to this plan? >
