(note: this is a reply to a post on bug 1111069 but bug 1096153 seems a more appropriate place to discuss this)
On 14/08/2025 14:05, Jonas Smedegaard wrote:
Seems to me that these are in need of a patch: * pushpin (too optimistic Debian dependency declared)
Already FTBFS and is not in testing, so I don't think it should be a blocker here.
If I understand you correctly, you are asking me to wait with the rustls-native-certs v0.6 -> v0.8 migration until you have completed some tungstenite migration. That's fine with me - please simply let me know, preferrably by posting to this bugreport, when that other migration is done.
When I started investigating the tungstenite packages (tungstenite, async-tungstenite and tokio-tungstenite) in light of the upcoming rustls-native-certs update. I came to the conclusion that I wanted to get them onto the current rustls stack, with functioning tests first. I initially thought this would involve semver bumps, but that turned out not to be required. I've now uploaded that work to unstable, and would like to have it in testing before we start the rustls-native-certs transition. async-tungstenite and tokio-tungstenite should now simply require patches to be dropped and the packaging regenerated (or dependencies manually updated). tungstenite will require a patch dropping and replacing with a patch cherry-picked from upstream. https://github.com/snapview/tungstenite-rs/commit/fb1f73b01a6aee6641bb22eb8c8deb892110120e I'm not expecting any of these changes to be difficult but I held off on preparing them until I'd dealt with any fallout from the switch to the rustls 0.23 stack.
