Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: esptool 0 -> 1 attrpath: esptool Checking auto update branch... [version] [version] skipping because derivation has updateScript [rustCrateVersion] [rustCrateVersion] No cargoHash found [golangModuleVersion] [golangModuleVersion] Not a buildGoModule package with vendorHash [npmDepsVersion] [npmDepsVersion] No npmDepsHash [updateScript] [updateScript] Success [updateScript] this derivation will be built: /nix/store/vplhlm2n36w7r117fl91x8d4rx6v51fc-packages.json.drv building '/nix/store/vplhlm2n36w7r117fl91x8d4rx6v51fc-packages.json.drv'... Going to be running update for following packages: - esptool-5.2.0 Press Enter key to continue... Running update for: Enqueuing group of 1 packages - esptool-5.2.0: UPDATING ... - esptool-5.2.0: DONE. Packages updated! Diff after rewrites: diff --git a/pkgs/by-name/es/esptool/package.nix b/pkgs/by-name/es/esptool/package.nix index d34418f9f0d3..4b0a7795d916 100644 --- a/pkgs/by-name/es/esptool/package.nix +++ b/pkgs/by-name/es/esptool/package.nix @@ -8,14 +8,14 @@ python3Packages.buildPythonApplication rec { pname = "esptool"; - version = "5.2.0"; + version = "5.3.dev1"; pyproject = true; src = fetchFromGitHub { owner = "espressif"; repo = "esptool"; tag = "v${version}"; - hash = "sha256-jXH1T/ey61eFcev4cuLQEVynO+/+BIqRndz+GutR/GU="; + hash = "sha256-G7j1vskYGlhC+k8qfw0fjsiYsthlQPzgc+b02nE8cXE="; }; postPatch = '' No auto update branch exists Successfully finished processing [check][nixpkgs-review] ## `nixpkgs-review` result Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review). Command: `nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'` Commit: `170d86c00e2c841dc0aafefb98cc160626720cab` --- ### `x86_64-linux`
:white_check_mark: 16 packages built:
Automatic update generated by [nixpkgs-update](https://github.com/nix-community/nixpkgs-update) tools. This update was made based on information from passthru.updateScript. meta.description for esptool is: ESP8266 and ESP32 serial bootloader utility meta.homepage for esptool is: https://github.com/espressif/esptool meta.changelog for esptool is: https://github.com/espressif/esptool/blob/v5.3.dev1/CHANGELOG.md ###### Updates performed - Ran passthru.UpdateScript ###### To inspect upstream changes ###### Impact Checks done --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 5.3.dev1 in filename of file in /nix/store/hmazg74v0r4lw86h7mf25ywlc4zr0c7z-esptool-5.3.dev1 ---
Rebuild report (if merged into master) (click to expand) ``` 10 total rebuild path(s) 10 package rebuild(s) First fifty rebuilds by attrpath esphome esptool python313Packages.lxmf python313Packages.nomadnet python313Packages.rns python314Packages.lxmf python314Packages.nomadnet python314Packages.rns rns ```
Instructions to test this update (click to expand) --- Either **download from the cache**: ``` nix-store -r /nix/store/hmazg74v0r4lw86h7mf25ywlc4zr0c7z-esptool-5.3.dev1 \ --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \ --option trusted-public-keys ' nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM= cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY= ' ``` (The nixpkgs-update cache is only trusted for this store-path realization.) For the cached download to work, your user must be in the `trusted-users` list or you can use `sudo` since root is effectively trusted. Or, **build yourself**: ``` nix-build -A esptool https://github.com/r-ryantm/nixpkgs/archive/170d86c00e2c841dc0aafefb98cc160626720cab.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/170d86c00e2c841dc0aafefb98cc160626720cab#esptool ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/hmazg74v0r4lw86h7mf25ywlc4zr0c7z-esptool-5.3.dev1 ls -la /nix/store/hmazg74v0r4lw86h7mf25ywlc4zr0c7z-esptool-5.3.dev1/bin ``` ---

### Pre-merge build results We have automatically built all packages that will get rebuilt due to this change. This gives evidence on whether the upgrade will break dependent packages. Note sometimes packages show up as _failed to build_ independent of the change, simply because they are already broken on the target branch. ## `nixpkgs-review` result Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review). Command: `nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'` Commit: `170d86c00e2c841dc0aafefb98cc160626720cab` --- ### `x86_64-linux`
:white_check_mark: 16 packages built:
--- ###### Maintainer pings cc @dotlambda for [testing](https://github.com/nix-community/nixpkgs-update/blob/main/doc/nixpkgs-maintainer-faq.md#r-ryantm-opened-a-pr-for-my-package-what-do-i-do). > [!TIP] > As a maintainer, if your package is located under `pkgs/by-name/*`, you can comment **`@NixOS/nixpkgs-merge-bot merge`** to automatically merge this update using the [`nixpkgs-merge-bot`](https://github.com/NixOS/nixpkgs/blob/master/ci/README.md#nixpkgs-merge-bot). https://api.github.com/repos/NixOS/nixpkgs/pulls/504910