Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: crun 1.29.1 -> 1.30 https://github.com/containers/crun/releases attrpath: crun 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/cr/crun/package.nix b/pkgs/by-name/cr/crun/package.nix index e578a68c8e94..969c1e0d2700 100644 --- a/pkgs/by-name/cr/crun/package.nix +++ b/pkgs/by-name/cr/crun/package.nix @@ -57,13 +57,13 @@ let in stdenv.mkDerivation (finalAttrs: { pname = "crun"; - version = "1.29.1"; + version = "1.30"; src = fetchFromGitHub { owner = "containers"; repo = "crun"; tag = finalAttrs.version; - hash = "sha256-KmwkiExekHozW84dmkcC8OW8AP11Fsqj2t/n+ZGXpB4="; + hash = "sha256-MpckXLN6ZI2iICD4OeZpYoyRmAxA3QDgrUt+gU2S3Bo="; fetchSubmodules = true; leaveDotGit = true; postFetch = '' 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: `efb9f61721bac901d498c35526bc4381ad752cb1` --- ### `x86_64-linux`
❌ 1 package failed to build:
✅ 18 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/containers/crun/releases. meta.description for crun is: Fast and lightweight fully featured OCI runtime and C library for running containers meta.homepage for crun is: https://github.com/containers/crun meta.changelog for crun is: https://github.com/containers/crun/releases/tag/1.30 ###### Updates performed - Version update ###### To inspect upstream changes ###### Impact Checks done --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 1.30 with grep in /nix/store/icl6qi7a5wyl3clj51naggy4zv131jww-crun-1.30 - found 1.30 in filename of file in /nix/store/icl6qi7a5wyl3clj51naggy4zv131jww-crun-1.30 ---
Rebuild report (if merged into master) (click to expand) ``` 27 total rebuild path(s) 21 package rebuild(s) First fifty rebuilds by attrpath ansible-builder ansible-navigator apx apx-gui buildah cri-o crun glances hci hercules-ci-agent krunvm out-of-tree pkgsRocm.ramalama podman podman-desktop python313Packages.ansible-builder python314Packages.ansible-builder ramalama sh4d0wup snouty ```
Instructions to test this update (click to expand) --- Either **download from the cache**: ``` nix-store -r /nix/store/icl6qi7a5wyl3clj51naggy4zv131jww-crun-1.30 \ --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 crun https://github.com/r-ryantm/nixpkgs/archive/efb9f61721bac901d498c35526bc4381ad752cb1.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/efb9f61721bac901d498c35526bc4381ad752cb1#crun ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/icl6qi7a5wyl3clj51naggy4zv131jww-crun-1.30 ls -la /nix/store/icl6qi7a5wyl3clj51naggy4zv131jww-crun-1.30/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: `efb9f61721bac901d498c35526bc4381ad752cb1` --- ### `x86_64-linux`
❌ 1 package failed to build:
✅ 18 packages built:
--- ###### Maintainer pings cc @saschagrunert @vdemeester 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/566551