fix pve-qemu source hash#232
Closed
KiaraGrouwstra wants to merge 1 commit into
Closed
Conversation
The meson subproject downloads in `postFetch` changed upstream, invalidating the fixed-output derivation hash.
Contributor
|
Not sure how it's possible considering that we refer to exact hash. If they were to force push something else with a different hash, it must've changed the hash, no? |
Contributor
|
Welp I think I hit it myself now: https://github.com/booxter/nix/actions/runs/26486950747/job/77996686907?pr=364 (different hash) |
Contributor
Author
|
yet a different one again huh. |
Contributor
|
@KiaraGrouwstra if you could try #238 and see if you get the same hash / are able to build / run. I suspect the drift came from |
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
2 participants
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.
looks like the hash changed upstream, invalidating the one we had here earlier.