Quoting Peter Green (2025-02-22 16:33:31) > > > It seems to me that you are lumping together two issues that can be > > tackled independently. It makes me nervous to do too many changes at > > once, especially when they require tight coordination like here: the > > patch to support rustls-pemfile 2 removes support for rustls-pemfile 1, > > which means the migration must be done at once across many packages. > > > > Please try isolate this as two indepent issues, one about rustls-pemfile > > and another about rustls-native-certs. It might turn out that we can do > > one more easily than the other, and that the other (whichever it turns > > out to be) cannot be achieved before the freeze. Better to then have one > > part migrated than have them both entangled and none of them finished in > > time for the freeze. > I think you may be right, time is running down and the updates > are taking more effort than I hoped to prepare, not because the > updates themselves are particularly difficult but because I keep > running into unrelated crap. The priority IMO is to get reqwest > fixed, and I think that is best acheived by updating rustls-pemfile > and semver-suffixing tokio-rustls and hyper-rustls. > > Since you have already patched rustls-platform-verifier to use the > old rustls-native-certs, the native-certs update seems a lower > priority, which can be left to post trixie.
This bugreport is about the two issues of patching rust-rustls-0.21 to upgrade rustls-pemfile and rustls-native-certs, respectively. I don't understand what you are saying about semver-suffixing but am pretty sure it is unrelated to rust-rustls-0.21: Please move discussions to the packages where they belong. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
