Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: conmon 2.1.13 -> 2.2.0 https://github.com/containers/conmon/releases attrpath: conmon 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/co/conmon/package.nix b/pkgs/by-name/co/conmon/package.nix index ad0840384a40..0e4ec33d029a 100644 --- a/pkgs/by-name/co/conmon/package.nix +++ b/pkgs/by-name/co/conmon/package.nix @@ -13,13 +13,13 @@ stdenv.mkDerivation (finalAttrs: { pname = "conmon"; - version = "2.1.13"; + version = "2.2.0"; src = fetchFromGitHub { owner = "containers"; repo = "conmon"; tag = "v${finalAttrs.version}"; - hash = "sha256-/Kt49c8a+R/+Z3KmFLpRTG+BdfPDAOEUtSis3alLAUQ="; + hash = "sha256-RVzjqTqw1NGAzXwiAKekByXA1aGgFrfwo3RtGKrfODk="; leaveDotGit = true; postFetch = '' cd $out 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: `04a70f1d57fbeab44405a5c06e5bb842ee2ef196` --- ### `x86_64-linux`
:white_check_mark: 25 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/conmon/releases. meta.description for conmon is: OCI container runtime monitor meta.homepage for conmon is: https://github.com/containers/conmon meta.changelog for conmon is: https://github.com/containers/conmon/releases/tag/v2.2.0 ###### Updates performed - Version update ###### To inspect upstream changes ###### Impact Checks done --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 2.2.0 with grep in /nix/store/lz4825883gii6s2v2dcxw9v2vnmw25mq-conmon-2.2.0 - found 2.2.0 in filename of file in /nix/store/lz4825883gii6s2v2dcxw9v2vnmw25mq-conmon-2.2.0 ---
Rebuild report (if merged into master) (click to expand) ``` 20 total rebuild path(s) 20 package rebuild(s) First fifty rebuilds by attrpath ansible-builder ansible-navigator apx apx-gui buildah conmon cri-o krunvm out-of-tree pkgsRocm.ramalama podman podman-desktop python313Packages.ansible-builder python314Packages.ansible-builder ramalama sh4d0wup singularity singularity-overriden-nixos udocker ```
Instructions to test this update (click to expand) --- Either **download from the cache**: ``` nix-store -r /nix/store/lz4825883gii6s2v2dcxw9v2vnmw25mq-conmon-2.2.0 \ --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 conmon https://github.com/r-ryantm/nixpkgs/archive/04a70f1d57fbeab44405a5c06e5bb842ee2ef196.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/04a70f1d57fbeab44405a5c06e5bb842ee2ef196#conmon ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/lz4825883gii6s2v2dcxw9v2vnmw25mq-conmon-2.2.0 ls -la /nix/store/lz4825883gii6s2v2dcxw9v2vnmw25mq-conmon-2.2.0/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: `04a70f1d57fbeab44405a5c06e5bb842ee2ef196` --- ### `x86_64-linux`
:white_check_mark: 25 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). --- Add a :+1: [reaction] to [pull requests you find important]. [reaction]: https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/ [pull requests you find important]: https://github.com/NixOS/nixpkgs/pulls?q=is%3Aopen+sort%3Areactions-%2B1-desc https://api.github.com/repos/NixOS/nixpkgs/pulls/479481