On 01/07/2024 07:21, Jonas Smedegaard wrote:
Quoting Peter Michael Green (2024-06-30 13:41:42)
I am aware that v2 is already pending in experimental, but given the
pace of transitioning to a new branch, it is helpful to have the
rng.fill() function available faster, for packages to prepare for the
transition, which is then in more cases possible to handle by loosenig
crate depenency to ">= 1.9, <= 2".
Done,
Excellent. Thanks!
Can you post in the bug for updating to 2.x when your packages
are ready and I'll look at the rust team ones.
Do you need something else/more than my confirmation post in February?
I see rsass and blocking are fixed, thanks. That leaves the async packages
Given that the async* packages seem to be increasingly important to the
rust ecosystem, I'd like confirmation that they can be fixed in a
coordinated manner.
Taking a look at them now, it looks like rust-async-executor will need
a coordinated upload, consisting of.
1. Taking the version from experimental
2. Bumping the Debian dependency on concurrent-queue to match the
cargo dependency.
3. Dropping patch 2001_fastrand.patch
4. Updating the debian dependencies on fastrand.
5. Uploading to unstable.
When I look at the patch used for fastrand 1.x it doesn't look
like it would be easilly adapted to support both the old and new versions.
In rust-async-lock, for the version in unstable, the Cargo dev-dependencies
allow the new version, but the Debian build/test dependencies do not. This is
fixed in the experimental version but the experimental version is
semver-breaking. So an update to the version in sid would seem sensible
to decouple the transitions.
