-
Notifications
You must be signed in to change notification settings - Fork 670
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
Cannot have nix 0.20
and 0.23
in same package due to conflicting bitflags
requirement
#1555
Comments
Fixes nix-rust#1555 None of the 1.3 features were being used
Fixes nix-rust#1555 None of the 1.3 features were being used Tested with `cargo +nightly generate-lockfile -Zminimal-versions`
Also if you could release |
See also #1548 |
The vendor/ directory will henceforth contain virginal code copied from upstream, and any necessary local modifications will only be made to src/bitflags.rs. Fixes nix-rust#1555
This is a new feature in Cargo 1.56.0, currently in beta. Once Nix's MSRV is >= 1.56.0, this feature will prevent future problems like the bitflags 1.3.0 fiasco. Issue nix-rust#1491 Issue nix-rust#1510 Issue nix-rust#1548 Issue nix-rust#1555
The vendor/ directory will henceforth contain virginal code copied from upstream, and any necessary local modifications will only be made to src/bitflags.rs. Fixes nix-rust#1555
Here's my proposed solution:
@aDotInTheVoid what do you think? |
The vendor/ directory will henceforth contain virginal code copied from upstream, and any necessary local modifications will only be made to src/bitflags.rs. Fixes nix-rust#1555
@aDotInTheVoid are you able to review the linked PR? |
I think this would solve the problem I'm facing with starship, I'll try in a couple of hours when I'm back at a keyboard |
I dont know how to test this actually. Sorry |
- possibly causing the CI codecov break for MacOS - ref: [MacOS: Undefined symbols for architecture x86_64](nix-rust/nix#1588) - ref: [Cannot have nix 0.20 and 0.23 in same package due to conflicting bitflags requirement](nix-rust/nix#1555) - ref: [Declare the MSRV in Cargo.toml](nix-rust/nix#1561)
Aleksey Kladov came up with a different solution, which we merged as #1593 . |
1561: Declare the MSRV in Cargo.toml r=rtzoeller a=asomers This is a new feature in Cargo 1.56.0, currently in beta. Once Nix's MSRV is >= 1.56.0, this feature will prevent future problems like the bitflags 1.3.0 fiasco. Issue #1491 Issue #1510 Issue #1548 Issue #1555 Co-authored-by: Alan Somers <asomers@gmail.com>
1561: Declare the MSRV in Cargo.toml r=rtzoeller a=asomers This is a new feature in Cargo 1.56.0, currently in beta. Once Nix's MSRV is >= 1.56.0, this feature will prevent future problems like the bitflags 1.3.0 fiasco. Issue #1491 Issue #1510 Issue #1548 Issue #1555 Co-authored-by: Alan Somers <asomers@gmail.com>
In
Cargo.toml
This leads to
Because
v0.23
needsbitflags > 1.3
butv0.20
needbitflags < 1.3
The text was updated successfully, but these errors were encountered: