Hi Markus, > I have prepared security updates for bookworm and trixie and could also fix > unstable via targeted patches. I would rather not package a new upstream > release though. I believe the release team would be in favor of addressing > these issues in unstable and testing first before I am going to fix bookworm > and trixie. What do you think?
I rediscovered work in progress staging in a directory on my machine to proceed to a dcmtk upstream upgrade in unstable. I've never finished, probably due to running into other duties AFK. I'm not sure how much work is left to have the package into an uploadable state. I'm okay with rebasing my work on top of your NMU/Team upload with targeted changes, so that getting the newer upstream release does not go in the way of shipping the necessary security patches. Thanks for your help with fixing the security issues of dcmtk in stable release! Have a nice day, :) -- .''`. Étienne Mollier <[email protected]> : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/1, please excuse my verbosity `- on air: Brahms - Double Cto pour violon et vcelle
signature.asc
Description: PGP signature
