ansible 0 -> 1 attrpath: ansible Checking auto update branch... [version] [version] skipping because derivation has updateScript [rustCrateVersion] [rustCrateVersion] No cargoSha256 or cargoHash found [golangModuleVersion] [golangModuleVersion] Not a buildGoModule package with vendorSha256 or vendorHash [npmDepsVersion] [npmDepsVersion] No npmDepsHash [updateScript] [updateScript] Success [updateScript] Going to be running update for following packages: - ansible-core-2.16.3 Press Enter key to continue... Running update for: - ansible-core-2.16.3: UPDATING ... - ansible-core-2.16.3: DONE. Packages updated! Diff after rewrites: diff --git a/pkgs/development/python-modules/ansible/core.nix b/pkgs/development/python-modules/ansible/core.nix index 7a2f7e5e6606..57d1a6b7ebf1 100644 --- a/pkgs/development/python-modules/ansible/core.nix +++ b/pkgs/development/python-modules/ansible/core.nix @@ -29,11 +29,11 @@ buildPythonPackage rec { pname = "ansible-core"; - version = "2.16.3"; + version = "2.16.4"; src = fetchPypi { inherit pname version; - hash = "sha256-dqh2WoWGBk7wc6KZVi4wj6LBgKdbX3Vpu9D2HUFxzbM="; + hash = "sha256-LNIIsJFZSMiL/60zHl0HCXtu3KGHLLUzdeUbZxnmoGA="; }; # ansible_connection is already wrapped, so don't pass it through No auto update branch exists Successfully finished processing cachix "/nix/store/3smh2g9m1z911x4likjb8b8mlld9pgm4-python3.11-ansible-core-2.16.4" [check][nixpkgs-review] Result of `nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }'` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
22 packages built:
Automatic update generated by [nixpkgs-update](https://github.com/ryantm/nixpkgs-update) tools. This update was made based on information from passthru.updateScript. meta.description for ansible is: Radically simple IT automation meta.homepage for ansible is: https://www.ansible.com meta.changelog for ansible is: https://github.com/ansible/ansible/blob/v2.16.4/changelogs/CHANGELOG-v2.16.rst ###### 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 2.16.4 with grep in /nix/store/3smh2g9m1z911x4likjb8b8mlld9pgm4-python3.11-ansible-core-2.16.4 - found 2.16.4 in filename of file in /nix/store/3smh2g9m1z911x4likjb8b8mlld9pgm4-python3.11-ansible-core-2.16.4 ---
Rebuild report (if merged into master) (click to expand) ``` 14 total rebuild path(s) 14 package rebuild(s) First fifty rebuilds by attrpath ansible ansible-later ansible-lint ansible_2_16 kargo molecule python311Packages.ansible-compat python311Packages.ansible-core python311Packages.ansible-kernel python311Packages.ansible-runner python311Packages.ansible-vault-rw python311Packages.molecule python311Packages.pytest-ansible python311Packages.pytest-testinfra ```
Instructions to test this update (click to expand) --- Either **download from Cachix**: ``` nix-store -r /nix/store/3smh2g9m1z911x4likjb8b8mlld9pgm4-python3.11-ansible-core-2.16.4 \ --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \ --option trusted-public-keys ' nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs= cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY= ' ``` (The Cachix cache is only trusted for this store-path realization.) For the Cachix 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 ansible https://github.com/r-ryantm/nixpkgs/archive/4c152d4800c53a148b41b69ecf814dbb8132ef53.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/4c152d4800c53a148b41b69ecf814dbb8132ef53#ansible ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/3smh2g9m1z911x4likjb8b8mlld9pgm4-python3.11-ansible-core-2.16.4 ls -la /nix/store/3smh2g9m1z911x4likjb8b8mlld9pgm4-python3.11-ansible-core-2.16.4/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. Result of `nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }'` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
22 packages built:
--- ###### Maintainer pings https://api.github.com/repos/NixOS/nixpkgs/pulls/292332