On 04.07.24 03:24, Jonas Smedegaard wrote:
Quoting Jonas Smedegaard (2024-06-18 22:58:59)
It seems these packages still need to be updated as well:
Here is the current status:

DONE in unstable:

* async-fs
   * v2.1.2 accepts async-lock v2+3 in unstable
   * v2.1.2 succeeds build-time testsuite and autopkgtests in unstable
* blocking
   * v1.6.1 accepts async-channel v1+2 in unstable
   * v1.6.1 succeeds build-time testsuite and autopkgtests in unstable
* criterion
   * v0.5.1 accepts smol v1+2 in unstable
   * v0.5.1 succeeds build-time testsuite and autopkgtests in unstable
* criterion-0.3
   * v0.3.6 accepts smol v1+2 in unstable
   * v0.3.6 succeeds build-time testsuite and autopkgtests in unstable

DONE in experimental, just need re-release for unstable:
[...]
* sluice
   * needs to accept async-channel v2 at least in experimental
   * needs custom testing: package lacks build-time testing
Patching sluice seems not trivial. Given that it's sole rdep is isahc, would you be ok with me filing a RM request for it if I patch isahc to use standard rust pipes ? imo this is the easiest option going forward. The code changes look more doable than patching sluice.
BROKEN for different reasons

* isahc
   * needs to accept async-channel v2 at least in experimental
   * needs to accept event-listener v5 at least in experimental
   * broken

If, as expected, testing of async-std turns succesfull, I am ready to
re-release to unstable all of the packages listed above that is
currently lingering in experimental.

Please tell when you are ready as well, for the packages above listed as
needing custom testing.  Only say so when they are *all* ready.

Kind regards, and thanks for all your help and patience,

Thanks :)

best,

werdahias

Reply via email to