-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
update etcher version - will update to electron v25 #274476
Conversation
This is my first pull request for a pkg update, please let me know if I did something wrong, or did not do something I was supposed to do. |
There is an unresolved problem upstream (balena-io/etcher#4138) that blocks all previous update attempts at #261626 and #263729. Have you actually tested flashing an image onto a USB stick using your build? |
No, I will look up how to build locally to test. |
Do you happen to know of any blog or easily digestible content related to building and testing packages for nikpgs? I found this in the docs https://github.com/jtojnar/nixpkgs-hammering, there is a lot to read though, and something more concise would be helpful if you know of anything. Update: this seems like viable candidate https://elatov.github.io/2022/01/building-a-nix-package/, leads to https://nixos.wiki/wiki/Nixpkgs/Contributing |
For contributions to nixpkgs, you can find some instructions in pkgs/README.md. Specifically, for building etcher, you'll need to run this from the root of the nixpkgs source tree: $ NIXPKGS_ALLOW_INSECURE=1 nix-build -A etcher
|
Oh no, I was hoping going to 25 would remove that security prompt. Thank you for this, I am doing now. I now see latest electron is v28. |
It builds, I will test package now with |
Seems when I comment out the permittedInsecurePackages config, that it is still referencing electron-19.1.9 when the subsequent error occurs. I ran this command: I imagine that a flake inputs override the -I flag, so I can try updating input to a local path. Update: I think I need to update the electron dependency version somehow in the PR. Local path works in flake, but still reverences v19.1.9. Looking into now, but I don't see how the dependency version is determined yet in etcher default.nix. I do see electron passed in as input though, so will trace. |
… with unexpected argument 'electron'
For doing this, you also have to change But what's interesting is that you've discovered that Electron 1.18.13 works with Electron 19. I'll check whether this is the case on my machine, and if it is, we can definitely do the upgrade. |
I need to learn about all-packages.nix now, but was hoping this upgrade would move etcher to electron 25 also. |
This is not the case on my machine, unfortunately... Does Etcher report itself as 1.18.13 when clicked on the settings button? |
No, 1.18.2. I will restart machine and see if that changes anything. |
Builds have been taking a long time since removing etcher, clearing garbage, and restarting. I am going to put a pin in this for today. |
I won't have time to finish this so closing. |
Description of changes
balena-io/etcher@f38bca2 (patch: upgrade to electron 25, 2023-08-30)
balena-io/etcher@fb8ed5b (patch: refactor scanner, loader and flasher out of gui + upgrade to electron 25, 2023-08-30)
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.
👍 - Security related update
cc @wegank