Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: charls 2.4.2 -> 2.4.3 https://github.com/team-charls/charls/releases attrpath: charls 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/ch/charls/package.nix b/pkgs/by-name/ch/charls/package.nix index d62da5e9670f..d00e450b37f5 100644 --- a/pkgs/by-name/ch/charls/package.nix +++ b/pkgs/by-name/ch/charls/package.nix @@ -7,13 +7,13 @@ stdenv.mkDerivation (finalAttrs: { pname = "charls"; - version = "2.4.2"; + version = "2.4.3"; src = fetchFromGitHub { owner = "team-charls"; repo = "charls"; tag = finalAttrs.version; - hash = "sha256-c1wrk6JLcAH7TFPwjARlggaKXrAsLWyUQF/3WHlqoqg="; + hash = "sha256-U21SdVRTPNI5BFGOyM3Y/ByKDP6ZI2g/BtAJYXH5Dv4="; }; postPatch = '' 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: `bdd52ca582637a7bd85f8c589d27c7f8b9a76697` --- ### `x86_64-linux`
:x: 4 packages failed to build:
:white_check_mark: 34 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/team-charls/charls/releases. meta.description for charls is: JPEG-LS library implementation in C++ meta.homepage for charls is: https://github.com/team-charls/charls ###### 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.4.3 with grep in /nix/store/aigr7ninri4z596kpps6v7gn9f85kk7l-charls-2.4.3 - found 2.4.3 in filename of file in /nix/store/aigr7ninri4z596kpps6v7gn9f85kk7l-charls-2.4.3 ---
Rebuild report (if merged into master) (click to expand) ``` 21 total rebuild path(s) 21 package rebuild(s) First fifty rebuilds by attrpath charls copyparty copyparty-full-buggy copyparty-most orthanc orthanc-framework orthanc-plugin-dicomweb python313Packages.fabio python313Packages.hdf5plugin python313Packages.highdicom python313Packages.nexusformat python313Packages.pillow-jpls python313Packages.pyjpegls python314Packages.fabio python314Packages.hdf5plugin python314Packages.highdicom python314Packages.nexusformat python314Packages.pillow-jpls python314Packages.pyjpegls silx ```
Instructions to test this update (click to expand) --- Either **download from the cache**: ``` nix-store -r /nix/store/aigr7ninri4z596kpps6v7gn9f85kk7l-charls-2.4.3 \ --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 charls https://github.com/r-ryantm/nixpkgs/archive/bdd52ca582637a7bd85f8c589d27c7f8b9a76697.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/bdd52ca582637a7bd85f8c589d27c7f8b9a76697#charls ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/aigr7ninri4z596kpps6v7gn9f85kk7l-charls-2.4.3 ls -la /nix/store/aigr7ninri4z596kpps6v7gn9f85kk7l-charls-2.4.3/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: `bdd52ca582637a7bd85f8c589d27c7f8b9a76697` --- ### `x86_64-linux`
:x: 4 packages failed to build:
:white_check_mark: 34 packages built:
--- ###### Maintainer pings cc @bcdarwin 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/496357