Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: bat-extras.core 2024.08.24-unstable-2025-02-22 -> 2024.08.24 https://github.com/eth-p/bat-extras/releases attrpath: bat-extras.core 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/g796mpcmmcmnkjkyb0n7s13hlmkm4jdk-packages.json.drv building '/nix/store/g796mpcmmcmnkjkyb0n7s13hlmkm4jdk-packages.json.drv'... Going to be running update for following packages: - bat-extras-2024.08.24-unstable-2025-02-22 Press Enter key to continue... Running update for: Enqueuing group of 1 packages - bat-extras-2024.08.24-unstable-2025-02-22: UPDATING ... - bat-extras-2024.08.24-unstable-2025-02-22: DONE. Packages updated! Diff after rewrites: diff --git a/pkgs/tools/misc/bat-extras/modules/core.nix b/pkgs/tools/misc/bat-extras/modules/core.nix index 30de45679491..a1f20e19fd87 100644 --- a/pkgs/tools/misc/bat-extras/modules/core.nix +++ b/pkgs/tools/misc/bat-extras/modules/core.nix @@ -12,7 +12,7 @@ }: stdenv.mkDerivation { pname = "bat-extras"; - version = "2024.08.24-unstable-2025-02-22"; + version = "0-unstable-2025-02-22"; src = fetchFromGitHub { owner = "eth-p"; 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: `b081deb59f4e4a3a7743514d956872d22e61da7c` --- ### `x86_64-linux`
:white_check_mark: 7 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 bat-extras.core is: Bash scripts that integrate bat with various command line tools meta.homepage for bat-extras.core is: https://github.com/eth-p/bat-extras ###### 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 0-unstable-2025-02-22 in filename of file in /nix/store/j6j8fwq1fla6ayilwg0kzniplqpbgdyp-bat-extras-0-unstable-2025-02-22 ---
Rebuild report (if merged into master) (click to expand) ``` 8 total rebuild path(s) 8 package rebuild(s) First fifty rebuilds by attrpath bat-extras.batdiff bat-extras.batgrep bat-extras.batman bat-extras.batpipe bat-extras.batwatch bat-extras.core bat-extras.prettybat ```
Instructions to test this update (click to expand) --- Either **download from the cache**: ``` nix-store -r /nix/store/j6j8fwq1fla6ayilwg0kzniplqpbgdyp-bat-extras-0-unstable-2025-02-22 \ --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 bat-extras.core https://github.com/r-ryantm/nixpkgs/archive/b081deb59f4e4a3a7743514d956872d22e61da7c.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/b081deb59f4e4a3a7743514d956872d22e61da7c#bat-extras.core ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/j6j8fwq1fla6ayilwg0kzniplqpbgdyp-bat-extras-0-unstable-2025-02-22 ls -la /nix/store/j6j8fwq1fla6ayilwg0kzniplqpbgdyp-bat-extras-0-unstable-2025-02-22/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: `b081deb59f4e4a3a7743514d956872d22e61da7c` --- ### `x86_64-linux`
:white_check_mark: 7 packages built:
--- ###### Maintainer pings cc @bbigras @PerchunPak 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/517378