Looking at the package tracker at
https://tracker.debian.org/pkg/rust-axum, it appears to me that
migration to testing is held up. It also occurs to me that debci
triggers autopkgtest against rust-tonic 0.10.2, which fails. I believe
that https://salsa.debian.org/debian/rust-axum/-/commit/103234e21b365f8b0f1f4fc09e136dd4f4243d86
would help debci and help the migration scripts finding that rust-tonic
and rust-axum need to migrate together.
Jonas, I'm happy to assist with uploads. Let me know your preference,
happy to NMU or maintainer upload at your choice.
Quoting Reinhard Tartler (2025-03-21 11:57:14)
Looking at the package tracker at
https://tracker.debian.org/pkg/rust-axum, it appears to me that
migration to testing is held up. It also occurs to me that debci
triggers autopkgtest against rust-tonic 0.10.2, which fails. I believe
that
https://salsa.debian.org/debian/rust-axum/-/commit/103234e21b365f8b0f1f4fc09e136dd4f4243d86
would help debci and help the migration scripts finding that
rust-tonic
and rust-axum need to migrate together.
Thanks for reporting, Reinhard!
I agree that Breaks seems to help migration, but only while rust-tonic
0.10 exists in a Debian branch: rust-tonic itself is pending migration
to 0.12 rendering the Breaks obsolete.
Question then is if it is worth the additional maturing time (ideally 3
days but potentially more) or it is better to "let it run its course".
On 2025-03-21 07:48, Jonas Smedegaard wrote:
Quoting Reinhard Tartler (2025-03-21 11:57:14)
Looking at the package tracker at
https://tracker.debian.org/pkg/rust-axum, it appears to me that
migration to testing is held up. It also occurs to me that debci
triggers autopkgtest against rust-tonic 0.10.2, which fails. I believe
that
https://salsa.debian.org/debian/rust-axum/-/commit/103234e21b365f8b0f1f4fc09e136dd4f4243d86
would help debci and help the migration scripts finding that
rust-tonic
and rust-axum need to migrate together.
Thanks for reporting, Reinhard!
I agree that Breaks seems to help migration, but only while rust-tonic
0.10 exists in a Debian branch: rust-tonic itself is pending migration
to 0.12 rendering the Breaks obsolete.
Question then is if it is worth the additional maturing time (ideally 3 days but potentially more) or it is better to "let it run its course".
In my experience with previous packages, without the breaks, the release
team needs to add a hint to britney to help detecting that both packages
need to migrate at the same time.
I'd be thrilled to be proven wrong on this point, though.
On 21/03/2025 13:16, Jonas Smedegaard wrote:[...]
Quoting Reinhard Tartler (2025-03-21 12:49:37)(...)
In my experience with previous packages, without the breaks, the release >> team needs to add a hint to britney to help detecting that both packages >> need to migrate at the same time.
@Blair, will you handle this, or do you prefer that I take over again,
now that my study pace has lowered again?
Fine for me either way. Let me know if a hand is needed.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 480 |
Nodes: | 16 (2 / 14) |
Uptime: | 250:23:22 |
Calls: | 9,532 |
Files: | 13,650 |
Messages: | 6,137,986 |