Hi Adam, Thanks for your fast response.
On 20-01-14 18:34:40, Adam D. Barratt wrote: > > Reading email@example.com  it seems that the date for 10.3 is > > not yet settled. > > You're behind on your reading I'm afraid - > https://lists.debian.org/debian-release/2020/01/msg00238.html Thanks for the hint, I missed this. > > Therefore: Would it be possible to still extend the already > > accepted proposed-update, at this point in time? > > > > We just did a sprint upstream and fixed several annoying bugs: > > If these are new changes, rather than updates to the fixes in the > package you already uploaded, then please open a new pu bug to cover > those. Will do -- I just wanted to check on the feasibility to get these into 10.3 still, that is, if I should extend the already accepted update (schleuder/3.4.0-2+deb10u1 merging in these new changes) or rather should prepare a new version, schleuder/3.4.0-2+deb10u2), on top of the already proposed one. > > The problems in question were reported upstream, not (yet) in the > > Debian BTS. The proposed code changes are minimal, targeted, guarded > > by tests and validated in production. > > Are the fixes included in the package currently in unstable? Not yet -- depending on the above, I could shortly (tomorrow, the latest) prepare and upload 3.4.1-2 pulling in these changes, or the next upstream release, 3.5.0-1 soonish, after the upstream release, in case it's too late for 10.3. Thanks again, Georg