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

install with --locked fails due to API change: update time to version >=0.3.35 #401

Open
KonradHoeffner opened this issue Sep 11, 2024 · 4 comments · May be fixed by #403
Open

install with --locked fails due to API change: update time to version >=0.3.35 #401

KonradHoeffner opened this issue Sep 11, 2024 · 4 comments · May be fixed by #403

Comments

@KonradHoeffner
Copy link

When I started cargo outdated today, I got an error with libgit2, so I updated it as described in the README with the --locked parameter as cargo install cargo-outdated --locked --force, however this results in the following error:

error[E0282]: type annotations needed for `Box<_>`
  --> /home/konrad/.cargo/registry/src/index.crates.io-6f17d22bba15001f/time-0.3.30/src/format_description/parse/mod.rs:83:9
   |
83 |     let items = format_items
   |         ^^^^^
...
86 |     Ok(items.into())
   |              ---- type must be known at this point
   |
   = note: this is an inference error on crate `time` caused by an API change in Rust 1.80.0; update `time` to version `>=0.3.35` by calling `cargo update`

I'm using cargo 1.83.0-nightly (c1fa840a8 2024-08-29) installed via Rustup on Arch Linux. Current cargo-outdated version is 0.15.0.
Removing the --locked parameter fixes the issue.
I guess you can fix this by either removing the --locked from the README or by creating a new release with an updated lockfile.

@KonradHoeffner
Copy link
Author

P.S.: Addressed by #397 and #398, please accept one of them and release a new version.

@MonterraByte MonterraByte linked a pull request Oct 3, 2024 that will close this issue
@barower
Copy link

barower commented Oct 22, 2024

cargo install --locked cargo-outdated still gives this error

@KonradHoeffner
Copy link
Author

Yeah, the maintainer seems to be inactive right now, I will try to reach out.

@Z1xus
Copy link

Z1xus commented Oct 27, 2024

cargo outdated got OUTDATED

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.

3 participants