Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: aws-lc 1.66.0 -> 1.67.0 https://github.com/aws/aws-lc/releases attrpath: aws-lc 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/6gjighj0b2mhlx9wvx3s0fc2vb4zn07w-packages.json.drv building '/nix/store/6gjighj0b2mhlx9wvx3s0fc2vb4zn07w-packages.json.drv'... Going to be running update for following packages: - aws-lc-1.66.0 Press Enter key to continue... Running update for: Enqueuing group of 1 packages - aws-lc-1.66.0: UPDATING ... - aws-lc-1.66.0: DONE. Packages updated! Diff after rewrites: diff --git a/pkgs/by-name/aw/aws-lc/package.nix b/pkgs/by-name/aw/aws-lc/package.nix index c267a1335ca2..29d3068f3676 100644 --- a/pkgs/by-name/aw/aws-lc/package.nix +++ b/pkgs/by-name/aw/aws-lc/package.nix @@ -11,13 +11,13 @@ }: stdenv.mkDerivation (finalAttrs: { pname = "aws-lc"; - version = "1.66.0"; + version = "1.67.0"; src = fetchFromGitHub { owner = "aws"; repo = "aws-lc"; rev = "v${finalAttrs.version}"; - hash = "sha256-OO9TWwaV/GlyrLl4C6oCFxIAeYfWjzvY7o//7OuoRDc="; + hash = "sha256-p58Re3HvBY/nzyCFvM5Ntx7Mb5OgcNQoZNloAJitDTY="; }; outputs = [ 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: `00fc425121e963f671d61c618a7ce6e3dbd3397d` --- ### `x86_64-linux`
:white_check_mark: 3 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 aws-lc is: General-purpose cryptographic library maintained by the AWS Cryptography team for AWS and their customers meta.homepage for aws-lc is: https://github.com/aws/aws-lc ###### Updates performed - Ran passthru.UpdateScript ###### To inspect upstream changes - [Release on GitHub](https://github.com/aws/aws-lc/releases/tag/v1.67.0) - [Compare changes on GitHub](https://github.com/aws/aws-lc/compare/v1.66.0...v1.67.0) ###### Impact Checks done --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 1.67.0 with grep in /nix/store/w22ybkid7p95v2vb2galqqyqhp1v730b-aws-lc-1.67.0 - found 1.67.0 in filename of file in /nix/store/w22ybkid7p95v2vb2galqqyqhp1v730b-aws-lc-1.67.0 ---
Rebuild report (if merged into master) (click to expand) ``` 2 total rebuild path(s) 2 package rebuild(s) First fifty rebuilds by attrpath aws-lc ```
Instructions to test this update (click to expand) --- Either **download from the cache**: ``` nix-store -r /nix/store/w22ybkid7p95v2vb2galqqyqhp1v730b-aws-lc-1.67.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 aws-lc https://github.com/r-ryantm/nixpkgs/archive/00fc425121e963f671d61c618a7ce6e3dbd3397d.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/00fc425121e963f671d61c618a7ce6e3dbd3397d#aws-lc ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/w22ybkid7p95v2vb2galqqyqhp1v730b-aws-lc-1.67.0 ls -la /nix/store/w22ybkid7p95v2vb2galqqyqhp1v730b-aws-lc-1.67.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: `00fc425121e963f671d61c618a7ce6e3dbd3397d` --- ### `x86_64-linux`
:white_check_mark: 3 packages built:
--- ###### Maintainer pings cc @theoparis 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/482910