add Cargo.lock #8
Merged
Conversation
This file contains 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
suggested practice for applications is to track this in git: https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html
|
Thank you for this great hint 👍 Now, I need to apply this fix to nearly all of my Tools 😢 This might take some days, 'cause I'm currently in a case. However, for Regards, Jan |
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.
Recently Void Linux has switched to requiring the
--lockedflag for cargo in package build steps, which results in ntdsextract2 failing to build.suggested practice for applications is to track this in git: https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html