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.

Sign up for GitHub

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

Jump to bottom

Multiple versions for dependency autocfg #472

Closed
ArekPiekarz opened this issue Feb 16, 2020 · 1 comment · Fixed by #474
Closed

Multiple versions for dependency autocfg #472

ArekPiekarz opened this issue Feb 16, 2020 · 1 comment · Fixed by #474

Comments

@ArekPiekarz
Copy link

Summary

Latest release of crossbeam-utils (0.7.0) depends on an old version of autocfg, which triggers the following Clippy warning when used together with other packages and slows down compilation:

warning: multiple versions for dependency `autocfg`: 1.0.0, 0.1.7
  |
  = note: `-W clippy::multiple-crate-versions` implied by `-W clippy::cargo`
  = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#multiple_crate_versions

The version from git already depends on autocfg 1, so it seems it could be fixed by just releasing a new version of crossbeam-utils - the last one is 3 months old.

Steps to reproduce

Add these dependencies to your project:
dirs 2.0.2, which depends on dirs-sys -> redox_users -> rust-argon2 -> crossbeam-utils -> autocfg 0.1.7
rust-ini 0.15.1, which depends on ordered-multimap -> hashbrown -> autocfg 1

Run: cargo clippy
@taiki-e
Copy link
Member

taiki-e commented Feb 16, 2020

Fixed in #460

This was referenced Feb 17, 2020
Closed
Merged
bors bot added a commit that referenced this issue Feb 17, 2020
@bors @jonhoo
Merge #474
556ebbc 
474: Patch release for all crossbeam crates. r=jeehoonkang a=jonhoo

This bumps the patch version for all sub-crates and the top-level crate and updates the changelogs with references to PRs where applicable. As far as I can tell, there are no breaking changes. The top-level crate has not change at all, though I bumped `rand` to `0.7` in all the crates, which I guess technically requires a patch bump if we do another release.

Fixes #473.
Closes #472.
Closes #468.
Closes #409.
Not sure if this also solves #347 by virtue of #458?

Co-authored-by: Jon Gjengset <jon@thesquareplanet.com>
bors bot added a commit that referenced this issue Feb 17, 2020
@bors @jonhoo
Merge #474
0210b05 
474: Patch release for all crossbeam crates. r=jeehoonkang a=jonhoo

This bumps the patch version for all sub-crates and the top-level crate and updates the changelogs with references to PRs where applicable. As far as I can tell, there are no breaking changes. The top-level crate has not change at all, though I bumped `rand` to `0.7` in all the crates, which I guess technically requires a patch bump if we do another release.

Fixes #473.
Closes #472.
Closes #468.
Closes #409.
Not sure if this also solves #347 by virtue of #458?

Co-authored-by: Jon Gjengset <jon@thesquareplanet.com>
@bors bors bot closed this as completed in #474 Feb 22, 2020
@bors bors bot closed this as completed in 6d6591a Feb 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Patch release for all crossbeam crates. jonhoo/crossbeam
2 participants
@ArekPiekarz @taiki-e