Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: unexpected warning with cargo install --locked due to outdated Cargo.lock [easy] [not urgent] #2914

Closed
brodycj opened this issue Aug 29, 2024 · 0 comments · Fixed by #2940

Comments

@brodycj
Copy link

brodycj commented Aug 29, 2024

Input C/C++ Header

N/A

Bindgen Invocation

cargo install bindgen-cli invocation

cargo install --locked bindgen-cli

back story

for rustls/rustls#2095 - running GitHub CI with cross on mutliple targets, I recall that build with aws-lc-rs / aws-lc-sys was ending with a message that I should install bindgen-cli with --locked flag (and --force, which seems absolutely not needed in this case) ... now encountered this warning ... would love to get this fixed, if possible

actual results

shows warning message:

    Updating crates.io index
  Installing bindgen-cli v0.70.1
    Updating crates.io index
warning: package `libc v0.2.154` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
    Updating crates.io index
   Compiling proc-macro2 v1.0.60
   Compiling quote v1.0.28
   Compiling libc v0.2.154
[...]

Expected Results

No warnings

alternative solutions

  • install without --locked, as recommended by the warning message
  • simply ignore the warning message

moving forward

Not super-urgent, I will try updating contributing an update for this.

emilio added a commit to emilio/rust-bindgen that referenced this issue Sep 25, 2024
@emilio emilio mentioned this issue Sep 25, 2024
github-merge-queue bot pushed a commit that referenced this issue Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant