Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: exfatprogs 1.3.1 -> 1.3.2 https://github.com/exfatprogs/exfatprogs/releases attrpath: exfatprogs Checking auto update branch... No auto update branch exists [version] [version] updated version and sha256 [rustCrateVersion] [rustCrateVersion] No cargoHash found [golangModuleVersion] [golangModuleVersion] Not a buildGoModule package with vendorHash [npmDepsVersion] [npmDepsVersion] No npmDepsHash [updateScript] [updateScript] skipping because derivation has no updateScript Diff after rewrites: diff --git a/pkgs/by-name/ex/exfatprogs/package.nix b/pkgs/by-name/ex/exfatprogs/package.nix index 37f3d88a06da..b8a13a4e687b 100644 --- a/pkgs/by-name/ex/exfatprogs/package.nix +++ b/pkgs/by-name/ex/exfatprogs/package.nix @@ -9,13 +9,13 @@ stdenv.mkDerivation (finalAttrs: { pname = "exfatprogs"; - version = "1.3.1"; + version = "1.3.2"; src = fetchFromGitHub { owner = "exfatprogs"; repo = "exfatprogs"; rev = finalAttrs.version; - sha256 = "sha256-AwY5TkQRfWjkkcleymNN580mKGxIdZ0O30tt6yBbo5M="; + sha256 = "sha256-eXJg4mMYydOpYVgOup7WJze0qx6RVkia0xSZOlG+IOQ="; }; nativeBuildInputs = [ 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: `ab018f7d24c478ea54902a3056393615025d67cf` --- ### `x86_64-linux`
:white_check_mark: 15 packages built:
Automatic update generated by [nixpkgs-update](https://github.com/nix-community/nixpkgs-update) tools. This update was made based on information from https://github.com/exfatprogs/exfatprogs/releases. meta.description for exfatprogs is: exFAT filesystem userspace utilities meta.homepage for exfatprogs is: https://github.com/exfatprogs/exfatprogs ###### Updates performed - Version update ###### To inspect upstream changes - [Release on GitHub](https://github.com/exfatprogs/exfatprogs/releases/tag/1.3.2) - [Compare changes on GitHub](https://github.com/exfatprogs/exfatprogs/compare/1.3.1...1.3.2) ###### Impact Checks done --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 1.3.2 with grep in /nix/store/yqvmfqqkigffj1xxwj3amzbcx5jqn6pb-exfatprogs-1.3.2 - found 1.3.2 in filename of file in /nix/store/yqvmfqqkigffj1xxwj3amzbcx5jqn6pb-exfatprogs-1.3.2 ---
Rebuild report (if merged into master) (click to expand) ``` 8 total rebuild path(s) 8 package rebuild(s) First fifty rebuilds by attrpath calamares calamares-nixos exfatprogs gparted-full kdePackages.kpmcore kdePackages.partitionmanager tparted ```
Instructions to test this update (click to expand) --- Either **download from the cache**: ``` nix-store -r /nix/store/yqvmfqqkigffj1xxwj3amzbcx5jqn6pb-exfatprogs-1.3.2 \ --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 exfatprogs https://github.com/r-ryantm/nixpkgs/archive/ab018f7d24c478ea54902a3056393615025d67cf.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/ab018f7d24c478ea54902a3056393615025d67cf#exfatprogs ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/yqvmfqqkigffj1xxwj3amzbcx5jqn6pb-exfatprogs-1.3.2 ls -la /nix/store/yqvmfqqkigffj1xxwj3amzbcx5jqn6pb-exfatprogs-1.3.2/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: `ab018f7d24c478ea54902a3056393615025d67cf` --- ### `x86_64-linux`
:white_check_mark: 15 packages built:
--- ###### Maintainer pings cc @yuannan 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/498473