Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: catboost 0 -> 1 attrpath: catboost 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/9f8pvr24rz5xfd6kzd6n96bs6fd6sx5d-packages.json.drv building '/nix/store/9f8pvr24rz5xfd6kzd6n96bs6fd6sx5d-packages.json.drv'... Going to be running update for following packages: - catboost-1.2.10 Press Enter key to continue... Running update for: Enqueuing group of 1 packages - catboost-1.2.10: UPDATING ... - catboost-1.2.10: DONE. Packages updated! Diff after rewrites: diff --git a/pkgs/by-name/ca/catboost/package.nix b/pkgs/by-name/ca/catboost/package.nix index 197137aa33d9..e3fd14458b7d 100644 --- a/pkgs/by-name/ca/catboost/package.nix +++ b/pkgs/by-name/ca/catboost/package.nix @@ -28,13 +28,13 @@ in stdenv.mkDerivation (finalAttrs: { pname = "catboost"; - version = "1.2.10"; + version = "1.2.10rc1"; src = fetchFromGitHub { owner = "catboost"; repo = "catboost"; tag = "v${finalAttrs.version}"; - hash = "sha256-z68vflYgO3cWeOkb417Gyco1Fqb98ulyRgI+OS+B4is="; + hash = "sha256-/Yl8wijvHxqWQ6IgkiWARpw3HphRW8J3suDlxdhAO8w="; }; postPatch = '' 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: `8f64fba28fcce41aa9cb2529fee8e8c72bb02e73` --- ### `x86_64-linux`
:white_check_mark: 6 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 catboost is: High-performance library for gradient boosting on decision trees meta.homepage for catboost is: https://catboost.ai meta.changelog for catboost is: https://github.com/catboost/catboost/releases/tag/v1.2.10rc1 ###### 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 1.2.10rc1 in filename of file in /nix/store/zaxk0jp38py57ikaza944vlqsijwk7sf-catboost-1.2.10rc1 ---
Rebuild report (if merged into master) (click to expand) ``` 4 total rebuild path(s) 4 package rebuild(s) First fifty rebuilds by attrpath catboost python313Packages.catboost python314Packages.catboost ```
Instructions to test this update (click to expand) --- Either **download from the cache**: ``` nix-store -r /nix/store/zaxk0jp38py57ikaza944vlqsijwk7sf-catboost-1.2.10rc1 \ --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 catboost https://github.com/r-ryantm/nixpkgs/archive/8f64fba28fcce41aa9cb2529fee8e8c72bb02e73.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/8f64fba28fcce41aa9cb2529fee8e8c72bb02e73#catboost ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/zaxk0jp38py57ikaza944vlqsijwk7sf-catboost-1.2.10rc1 ls -la /nix/store/zaxk0jp38py57ikaza944vlqsijwk7sf-catboost-1.2.10rc1/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: `8f64fba28fcce41aa9cb2529fee8e8c72bb02e73` --- ### `x86_64-linux`
:white_check_mark: 6 packages built:
--- ###### Maintainer pings cc @PlushBeaver @natsukium 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/519592