Quoting Jonas Smedegaard (2024-06-18 22:58:59) > It seems these packages still need to be updated as well:
Here is a more complete list of branch transisioning entanglements for
async-broadcast, async-channel, async-lock, async-process, event-listener
and smol.
DONE for unstable:
* blocking
* v1.4.1 accepts async-channel v1+2 in unstable
* v1.4.1 accepts async-lock v2+3 in unstable
DONE for experimental, just need re-release for unstable:
* async-channel
* involves branch transition: v1 -> v2
* v2.3.1 accepts event-listener v5 in experimental
(via event-listener-strategy)
* v2.3.1 succeeds build-time testsuite in experimental
* async-executor
* v1.12.0 stops needing async-lock v2 in experimental
* v1.12.0 succeeds build-time testsuite in experimental
* async-lock
* involves branch transition: v2 -> v3
* v3.4.0 accepts event-listener v5 in experimental
* v3.4.0 succeeds build-time testsuite in experimental
* async-process
* involves branch transition: v1 -> v2
* v2.2.3 accepts async-channel v2 in experimental
* v2.2.3 accepts async-lock v2+3 in experimental
* v2.2.3 accepts event-listener v5 in experimental
* v2.2.3 succeeds build-time testsuite in experimental
* async-std
* needs to accept async-channel v2 at least in experimental
* needs to accept async-lock v3 at least in experimental
* needs to accept async-process v2 at least in experimental
* awaits librust-async-global-executor-dev
* event-listener
* involves branch transition: v2 -> v5
* v5.3.1 succeeds build-time testsuite in experimental
TODO:
* async-broadcast
* involves branch transition: v0.5 -> v0.7
* v0.7.0 accepts event-listener v5 in experimental
* needs custom testing: package lacks build-time testing
* async-fs
* v2.1.2 accepts async-lock v2+3 in unstable
* v2.1.2 succeeds build-time testsuite in unstable
* awaits possible revert if unstable zbus cannot fit new branch
<https://bugs.debian.org/1074107>
* async-global-executor
* needs to accept async-channel v2 at least in experimental
<https://bugs.debian.org/1074067>
<https://bugs.debian.org/1074114>
* needs to accept async-lock v3 at least in experimental
* needs custom testing: package lacks build-time testing
* async-io
* v2.3.3 accepts async-lock v3 in experimental
* needs custom testing: package lacks build-time testing
* async-mutex
* v1.4.0 accepts event-listener v5 in experimental
* needs custom testing: package lacks build-time testing
* blocking
* v1.6.1 accepts async-channel v2 in experimental
* criterion
* needs to accept smol v2 at least in experimental
* criterion-0.3
* needs to accept smol v2 at least in experimental
(or obsoletion: https://bugs.debian.org/1074104)
* crosstermion
* v0.14.0 accepts async-channel v2 in experimental, sloppily
* needs custom testing: package lacks build-time testing
* event-listener-strategy
* v0.5.2 accepts event-listener v5 in experimental
* needs custom testing: package lacks build-time testing
* fs4
* needs to accept smol v2 at least in experimental
* needs custom testing: package lacks build-time testing
* gst-plugin-gtk4
* needs to accept async-channel v2 at least in experimental
* needs custom testing: package lacks build-time testing
* if-watch
* needs to accept smol v2 at least in experimental
* isahc
* needs to accept async-channel v2 at least in experimental
* needs to accept event-listener v5 at least in experimental
* sluice
* needs to accept async-channel v2 at least in experimental
* needs custom testing: package lacks build-time testing
* smol
* involves branch transition: v1 -> v2
* v2.0.0 accepts async-channel v1+2 in experimental
* v2.0.0 accepts async-fs v1+2 in experimental
* v2.0.0 accepts async-lock v3 in experimental
* awaits blocking
* sqlx-core
* v0.7.3 accepts event-listener v5 in experimental
* needs custom testing: package lacks build-time testing
* zbus
* needs to accept async-fs in unstable
<https://bugs.debian.org/1074107>
* needs to accept event-listener v5 at least in experimental
* needs custom testing: package lacks build-time testing
My next tasks is to get smol working in experimental, and then the
packages depending on smol as well.
After that, I am ready to "flip the switch" and re-release all packages
now in experimental for unstable. But I would be quite frustrated if it
turns out that the sloppy packaging style by the Rust team has caused
some breakage goes undetected, so I will wait for your guys from the Rust
team to state explicitly here in this bugreport, that you believe that
all the packages listed above as "needs custom testing" are good to go.
Kind regards,
- 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
