fix: Workaround E0119 trait conflict introduced by time v0.3.48#438
Closed
ReenigneCA wants to merge 1 commit into
Closed
fix: Workaround E0119 trait conflict introduced by time v0.3.48#438ReenigneCA wants to merge 1 commit into
ReenigneCA wants to merge 1 commit into
Conversation
time 0.3.48 creates trait conflicts. This allows cargo update to work properly until the difference with rcgen is worked out fully.
Member
|
This would be worse than the current state, where users can simply pin a non-broken (either the previous, or subsequent, versions). |
Member
|
This should happen in your lockfile. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Constrains the
timedependency inCargo.tomlto fix a broken build caused by the recenttimev0.3.48release.time
0.3.48introduces an upstream trait implementation that conflicts withrcgen's genericimpl<T: Into<String>> From<T>bounds forOtherNameValueandDnValue. Without this constraint, runningcargo update && cargo buildfails with anE0119: conflicting implementationserror.Updating Cargo.toml to reject time 0.3.48 fixes
cargo updatefor rcgen and downstream users until the incompatibility can be resolved.rustc error context