failed to download replaced source registry `crates-io` Caused by: failed to verify the checksum of `bitflags v1.3.2 (registry `kellnr-cratesio`)` about kellnr HOT 5 CLOSED

One possible problem could be that the crates where downloaded before from crates.io and now they are downloaded from your kellnr proxy. Unfortunately cargo is not able to work with "mixed" indicies.

Can you try to delete your Cargo.lock and clean your old index cache with rm -rf ~/.cargo/registry/* and check if the issue persists?

from kellnr.

One possible problem could be that the crates where downloaded before from crates.io and now they are downloaded from your kellnr proxy. Unfortunately cargo is not able to work with "mixed" indicies.

Can you try to delete your Cargo.lock and clean your old index cache with rm -rf ~/.cargo/registry/* and check if the issue persists?

Sorry, I forgot to mention, the issue persists even after deleting the registry directory and running 'cargo clean'

from kellnr.

If if it's not a mixed index, I don't have another idea, but I'll try to help debug the issue.

Can you provide logs from Kellnr (log level = trace) and from cargo when you run it with a verbose flag? Maybe there is a hint somewhere in the logs.

from kellnr.

when running with trace kellnr log level I get:

...
2024-01-14T16:35:21.769952Z DEBUG registry::cratesio_api: Crate not found on disk, downloading from crates.io
2024-01-14T16:35:21.845836Z TRACE registry::cratesio_api: Downloading crate: unicase (2.7.0) from path /opt/kdata/crates/unicase-2.7.0.crate
2024-01-14T16:35:21.846510Z TRACE registry::cratesio_api: Crate found in cache, skipping download

cargo run --verbose
doesn't return any other errors than:

error: failed to download replaced source registry `crates-io`
Caused by:
failed to verify the checksum of `unicase v2.7.0 (registry `kellnr-cratesio`)`

I've removed ~/.cargo/registry
I've ran cargo clean
I've deleted Cargo.lock

from kellnr.

I'm out of ideas, as I cannot reproduce the issue. I'll close the issue, but if you find out what the issue is, or have more information available, feel free to reopen it.

from kellnr.