On Fri, May 24, 2019 at 12:45:15AM +0200, Thorsten Glaser wrote: > On Thu, 23 May 2019, Emmanuel Bourg wrote: > > > than 11.0.3+7, or patch the existing version. Since testing is currently > > frozen and difficult to update until the release of Buster, it leaves > > only the patch solution. > > That being said, it’s also not permitted to add in a patch anything > to a backport that’s not in the base (n+1) version, except things > necessary to do the backporting itself. Emmanuel, I see that openjdk-11 11.0.3+1-1~bpo9+2 has been accepted in stable backports [1], so the (smallish) patch to bring the code up to the +7/-ga tag was deemed allowable after all. Thank you for driving this for stable. I think it is important to get a "-ga" versioned package into Buster because 11.0.3+1 is potentially confusing - it seems like it's version *after* 11.0.3, when in fact it's an EA release. According to the developer's reference for t-p-u [2], this case meets all of the criteria. And once that version is Buster, we can also update the version number in stable backports. Can folks think of any reasons why we shouldn't go ahead and upload to testing-proposed-updates for Buster? If there are any concerns, please speak up. Otherwise, I'll work on an upload this weekend. Thanks, tony [1] https://tracker.debian.org/news/1040268/accepted-openjdk-11-11031-1bpo92-source-amd64-all-into-stretch-backports-backports-policy-stretch-backports/ [2] https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#t-p-u
Attachment:
signature.asc
Description: PGP signature