treewide: update cargoSha256 hashes for cargo-vendor upgrade #62047
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
|
OfBorg will fail here, because some of the packages whose dependencies I’ve fixed are broken for other reasons. Not a reason to avoid merging. |
|
Looks like it's purely just |
|
I don't think staging is needed though. This is just ~100 rebuilds of packages without any reverse dependencies, which shouldn't be a problem on master. As far as I understand, staging is mostly useful to group together mass updates like stdenv or other packages deep down the dependency tree. |
|
I don't think staging is needed though.
Agreed. I expected the rebuild count to be higher.
|
|
Merged to master as 062210b. |
10 tasks
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.
Motivation for this change
A recent upgrade of cargo-vendor changed its output slightly, which broke all
cargoSha256hashes in nixpkgs. See #60668 for more information.Since then, a few hashes have been fixed in master by hand, but there were a lot still to do, so I did all of the ones left over with some scripts I wrote. Once this is merged, I can run the same scripts on the release branch that the cargo-vendor upgrade has made it into.
I’ve tested that this doesn’t break any builds on master. The actual target of the PR is staging, though, because of the number of rebuilds. The one hash I wasn’t able to update was
habitat’s, because it’s currently broken and the build doesn’t get far enough to produce a hash anyway.Things done
sandboxinnix.confon non-NixOS)nix-shell -p nix-review --run "nix-review wip"./result/bin/)nix path-info -Sbefore and after)