Hi, > However, this version has not been updated since the Bullseye release > (whereas the up to date version is available in testing).
right, someone has to do a stable or stable-security upload; probably the latter, from how this has been handed for other JDK versions before. Primary contact for this is Doko (Cc’d, though he probably also reads the list?); I assume from the release note snippet that this has been ok’d by release/security teams beforehand. > There is a bug report [2] for this problem, but it seems to have been > closed without any reason. No, its version tracking merely marks a version that’s not in stable as fixing this bug, but it’s still affecting stable/bullseye. The BTS can be confusing like that ;-) > version. You can find lots of tutorials on the Internet explaining how Yeah, well, those tutorials… *sigh* having taken over openjdk-8 for a while I ran into some counter-productive advice from them as well. But there’s not much one can do about them, except of course provide working things for the good case. > Is an upgrade of openjdk-17 still planned for Bullseye? I’d assume so, though you might have noticed the snippet did say not every update is guaranteed to be made available. bye, //mirabilos -- Infrastrukturexperte • tarent solutions GmbH Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/ Telephon +49 228 54881-393 • Fax: +49 228 54881-235 HRB AG Bonn 5168 • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg **************************************************** /⁀\ The UTF-8 Ribbon ╲ ╱ Campaign against Mit dem tarent-Newsletter nichts mehr verpassen: ╳ HTML eMail! Also, https://www.tarent.de/newsletter ╱ ╲ header encryption! ****************************************************
