Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: cef-binary 0 -> 1 attrpath: cef-binary 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/1wwnln3hwzp7q649is8f453y7rh07z6n-packages.json.drv building '/nix/store/1wwnln3hwzp7q649is8f453y7rh07z6n-packages.json.drv'... Going to be running update for following packages: - cef-binary-142.0.10 Press Enter key to continue... Running update for: Enqueuing group of 1 packages - cef-binary-142.0.10: UPDATING ... - cef-binary-142.0.10: DONE. Packages updated! Diff after rewrites: diff --git a/pkgs/by-name/ce/cef-binary/package.nix b/pkgs/by-name/ce/cef-binary/package.nix index 4a0872d16a22..c76f259ca7dc 100644 --- a/pkgs/by-name/ce/cef-binary/package.nix +++ b/pkgs/by-name/ce/cef-binary/package.nix @@ -29,13 +29,13 @@ libx11, libxshmfence, libxcb, - version ? "142.0.10", - gitRevision ? "29548e2", - chromiumVersion ? "142.0.7444.135", + version ? "146.0.6", + gitRevision ? "68649e2", + chromiumVersion ? "146.0.7680.154", buildType ? "Release", srcHashes ? { - aarch64-linux = "sha256-wUCXk5Nqgzu0q0PvV8a2AKF3h4YxxTeaP2yVecrf0j8="; - x86_64-linux = "sha256-pFMHjj4MktjnX3g03sgLqgai4X/lF29Phmduf7a+KfM="; + aarch64-linux = "sha256-jmScu9v3qsShYZx3YpJdSs/o1Gork9NdGtXouaYrhgI="; + x86_64-linux = "sha256-ZRSw6tnhYyVkshVHKM3wiPsEsyXkqF4m5mEXQDRw15o="; }, }: An auto update branch exists with message `cef-binary: 142.0.10 -> 145.0.28`. New version is 146.0.6. The auto update branch does not match or exceed the new version. 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: `5163cbc9368f18dd82ff279f5860b18485c736f2` --- ### `x86_64-linux`
:x: 2 packages failed to build:
:white_check_mark: 1 package 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 cef-binary is: Simple framework for embedding Chromium-based browsers in other applications meta.homepage for cef-binary is: https://cef-builds.spotifycdn.com/index.html ###### 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 146.0.6 with grep in /nix/store/3dsi8n0v6y2zxh0ccxdw1xyzvp7apfmq-cef-binary-146.0.6 - found 146.0.6 in filename of file in /nix/store/3dsi8n0v6y2zxh0ccxdw1xyzvp7apfmq-cef-binary-146.0.6 ---
Rebuild report (if merged into master) (click to expand) ``` 4 total rebuild path(s) 4 package rebuild(s) First fifty rebuilds by attrpath cef-binary graphite stremio-linux-shell ```
Instructions to test this update (click to expand) --- Either **download from the cache**: ``` nix-store -r /nix/store/3dsi8n0v6y2zxh0ccxdw1xyzvp7apfmq-cef-binary-146.0.6 \ --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 cef-binary https://github.com/r-ryantm/nixpkgs/archive/5163cbc9368f18dd82ff279f5860b18485c736f2.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/5163cbc9368f18dd82ff279f5860b18485c736f2#cef-binary ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/3dsi8n0v6y2zxh0ccxdw1xyzvp7apfmq-cef-binary-146.0.6 ls -la /nix/store/3dsi8n0v6y2zxh0ccxdw1xyzvp7apfmq-cef-binary-146.0.6/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: `5163cbc9368f18dd82ff279f5860b18485c736f2` --- ### `x86_64-linux`
:x: 2 packages failed to build:
:white_check_mark: 1 package built:
--- ###### Maintainer pings cc @puffnfresh 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). Updated existing PR https://api.github.com/repos/NixOS/nixpkgs/pulls/455980