Closed acgetchell closed 4 weeks ago
Duplicate of #423
Note, a later version of libc has been released, so is there an issue here?
uuid v1.8.0 uses this crate, so presumably once they update this will be resolved.
@acgetchell you should be able to use the correct version of libc without any crates needing to do anything, as 0.2.155 is compatible with 0.2.154
Ah, thanks. I'm not a direct consumer, though. Unless there's something I haven't understood from the Cargo book, I didn't see a way to specify libc 0.2.155 directly other than mucking around with Cargo.lock, which seems to be disfavored.
@acgetchell if the problematic Cargo.lock
file is in your project, you can either delete and regenerate it or call cargo update
to bump your dependencies. This page explains how all that works: https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html
This was flagged in actions-rust-lang/audit@v1.