-
-
Notifications
You must be signed in to change notification settings - Fork 82
Nix update #490
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
Nix update #490
Conversation
This and #487 are partially redundant EDIT: actually they might not be, the hashes do seem to be different. |
manually trying this PR out gave me this very dumbfounding message, I am all weirded out |
It looks like the updated hash in this PR isn't correct. @Trivaris if you want, I can pull the changes to |
nix build .#millennium
nix build .# will compile successfully on the Im currently using my fork as a flake input to my nixos configuration and it works perfectly fine |
I did at some point accidentally sync my fork with the upstream repo, but reversed that immediatly, thought this pull request seems to still have that commit, im getting on that right now |
I'm getting the same error @Neubulae reported EDIT: or effectively the same, at least |
I removed the failing commit, the builds still pass on my end, but what I suspect is happening is that at some point the pnpm dependencies are changed to different versions of themselves, be it by using already installed versions or the upstream repo updating it, which results in a different hash, which is causing that error. |
I'm slightly confused now, whatever change you just made doesn't fix the build error, the hash you have for the |
Millennium on nix-update via △
❯ nix build .#millennium
Millennium on nix-update via △ took 3s
❯ nix build .#
Millennium on nix-update via △ took 3s
❯ nix build .#assets
Millennium on nix-update via △ took 3s
❯ I didn't change anything per se, I just rolled back a sync of the upstream repo, which updated the dependencies, thus changing the hashes. On my end the builds are still passing and I do not know what else would or could change that Though we can do what you suggested here and split these concerns into different prs,
What I will say though is that automatically updating the hashes does kind of go against nix's philosophy of perfectly reproducible builds, as it depends on outside variables and that change would make this flake impure EDIT: Sorry, I misunderstood the purpose of that script, its perfectly fine, sorry |
all good, I'm not 100% sure it's functioning properly atm.
What happens if you change the |
The Nix maintainer on Millennium is very inactive, and I don't use Nix, nor do I know anything about it. |
Moved to #487 |
Nix: factor out
system
, format Nix, and refresh pnpm hashesChanges
system = "x86_64-linux"
and reuse it acrossflake.nix
:${system}
forpackages
anddevShells
.inherit system
into the overlay.nixfmt-rfc-style
formatting across Nix files and minor tidy-ups:pnpm.fetchDeps
content-addressed hashes in:nix/assets.nix
nix/typescript/shims.nix
Rationale
Scope / Risk
system
from a single place