Tried to post this here , but I think something went wrong. Please delete that if possible, I can not access it Hi I am experiencing some weird issues with using gitea as a registry. I am not quite sure if this is a gitea problem, a cargo problem or some combination. I have a rust library function…

I think I might be getting closer here. Running CARGO_LOG=trace cargo build -vvv &> cargo.log yields this With the interesting part being checking freshness of fu/nc/function-generator index file version: Unknown slow path for "fu/nc/function-generator" json parsed registry function-generator/0.1.…

Crate version not found when using gitea as registry (new try)

quinedot November 6, 2024, 8:24pm 4

(Temporary technical issue, see here.)

Topic		Replies	Views
Cargo unable to update registry with "wrong pack signature" help	9	1357	October 8, 2022
Rust update seems to have broken imgui-rs help	4	920	January 12, 2023
'cargo publish' to a private git repository?	5	1740	December 25, 2023
Crates.io compatibility with old cargo help	27	4836	January 12, 2023
Suggestions tracking down not-found crate? help	3	543	January 12, 2023

Crate version not found when using gitea as registry (new try)

Related topics