-> Jonas Smedegaard <[email protected]>, 2025-08-21T14:40:19+0200 ->
Quoting Blair Noctis (2025-08-21 14:11:32)-> Jonas Smedegaard, 2025-08-19 18:27:08 +0200 ->Package: atuin I would like to upgrade crate axum to v0.8. A package is available in experimental, please adapt atuin to work with that, to prepare for the migration. A patch has been proposed upstream, which might be suitable: https://github.com/atuinsh/atuin/pull/2735Thanks for the heads-up. There is another similar notice from rustix, and there is the prost stack upgrade, so I'm expecting atuin to come up a bit late. IIRC that new versions in unstable don't break rdeps already in testing, please just go ahead. Otherwise I'll try to speed up.If by "come up a bit late" you mean that you expect atuin to be broken during the transition of multiple underlying library crates, then no, new library versions in unstable will not transition to testing until all dependencies and build-dependencies are satisfied in testing. Which means either a) all library transistion will be blocked from entering testing until atuin is also updated, or b) we can request removal from testing of atuin to speed up migrations, and then let it enter testing again when updated to work with the newer libraries. Makes sense? Or did I perhaps misunderstand what you were saying?
Let's be concrete and, say, if atuin is to lag behind this axum upgrade, is it going to prevent axum from migrating?
Since atuin is already in testing, if the answer is yes, that means a leaf package already in testing would prevent a package it depends on from migrating, even if the former has been distributed. My memory was vague here, hence the question.
I'll try to work on it in the weekend anyway, just that if the answer is no it'll allow me to slack off a bit more from $work. Don't worry, I can slack off in weekdays too ;p
-- ,Sdrager Blair Noctis 🇵🇸
OpenPGP_signature.asc
Description: OpenPGP digital signature
