universal-hash-0.6.0-rc.10 not updated to remove common::BlockSizes

[Harrygiel]

Following #2309 , universal-hash-0.6.0-rc.10 can't compile anymore:

error[E0432]: unresolved import common::BlockSizes
--> /home//.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/universal-hash-0.6.0-rc.10/src/lib.rs:16:29
|
16 | use common::{BlockSizeUser, BlockSizes, ParBlocksSizeUser, array::Array};
| ^^^^^^^^^^
| |
| no BlockSizes in the root
| help: a similar name exists in the module: BlockSizeUser

In the same way, ctr-0.10.0-rc.3 can't compile:
error[E0432]: unresolved import cipher::common::BlockSizes
--> /home//.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/ctr-0.10.0-rc.3/src/ctr_core.rs:7:14
|
7 | common::{BlockSizes, InnerUser, IvSizeUser},
| ^^^^^^^^^^
| |
| no BlockSizes in the root
| help: a similar name exists in the module: BlockSizeUser

Yet universal-hash src was updated 17 hours ago with a fix, but without a release tag.

For example, the following tree is then now broken:

crypto-common v0.2.1
└── universal-hash v0.6.0-rc.10
    └── polyval v0.7.0-rc.9
        └── ghash v0.6.0-rc.6
            └── aes-gcm v0.11.0-rc.3 (*)

Is it possible to tag a new version of universal-hash and ctr ?
Respectfully,

[newpavlov]

My intent is to cut proper (i.e. non-RC) releases of the universal-hash/cipher/digest crates in the near future. AEAD crates will stay in the RC status for the time being, since aead is likely to change a bit.

[Harrygiel]

@newpavlov I understand. Would you please be able to give an approximate time of release ?
It would help me measure how long will my project be down:

1. I can't rollback crypto-common as it allow the compilation of universal-hash, but break the compilation of rand => chacha20 => cipher => crypto-common (cipher 0.5 was yanked)
2. I can't rollback aes-gcm as the previous version was inadequate with my use case, and applying a fix would takes a lot of time.
3. I can't continue to test and compile universal-hash without using the main branch, which would potentially introduce instability in my tests.

This mean that i can't really work anymore on my project and I would greatly appreciate an approximate head up on the down time.
PS: This also mean that we can't check for potential regression or issues in a RC version of universal-hash and ctr until then

[newpavlov]

I hope it will take a day or two at most. #2317 is the first step.

[newpavlov]

For the time being I recommend using dependency patching. I think this should work for you:

[patch.crates-io]
universal-hash = { git = "https://github.com/RustCrypto/traits" }

[Harrygiel]

True: I will simulate a new RC by fixin the rev.
If anybody want to apply the same solution, this patch can also be needed:
ctr = { git = "https://github.com/RustCrypto/block-modes", rev = "3dbbcf1" }