Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: blender 0 -> 1
attrpath: blender
Checking auto update branch...
[version]
[version] generic version rewriter does not support multiple hashes
[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/sfzd3q5vph8qvlv6g2y3dr5x9syx2jya-packages.json.drv
building '/nix/store/sfzd3q5vph8qvlv6g2y3dr5x9syx2jya-packages.json.drv'...
Going to be running update for following packages:
- blender-5.0.1
Press Enter key to continue...
Running update for:
Enqueuing group of 1 packages
- blender-5.0.1: UPDATING ...
- blender-5.0.1: DONE.
Packages updated!
Diff after rewrites:
diff --git a/pkgs/by-name/bl/blender/package.nix b/pkgs/by-name/bl/blender/package.nix
index 33630f2a2b26..6e24c05c49fe 100644
--- a/pkgs/by-name/bl/blender/package.nix
+++ b/pkgs/by-name/bl/blender/package.nix
@@ -118,12 +118,12 @@ in
stdenv'.mkDerivation (finalAttrs: {
pname = "blender";
- version = "5.0.1";
+ version = "4.5.6";
src = fetchzip {
name = "source";
url = "https://download.blender.org/source/blender-${finalAttrs.version}.tar.xz";
- hash = "sha256-fNnQRfGfNc7rbk8npkcYtoAqRjJc6MaV4mqtSJxd0EM=";
+ hash = "sha256-kw0dlTX97LcrhgTG3CDBE74H5iPljM87X4zeWKLdetQ=";
};
# Minimal backport of hiprt 3.x support from https://projects.blender.org/blender/blender/pulls/144889
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: `bfaf60fad17a25241c9e5db0bc47a05b49cbaa72`
---
### `x86_64-linux`
:white_check_mark: 2 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 blender is: 3D Creation/Animation/Publishing System
meta.homepage for blender is: https://www.blender.org
###### Updates performed
- Ran passthru.UpdateScript
###### To inspect upstream changes
###### Impact
Checks done
---
- built on NixOS
> [!CAUTION]
> A test defined in `passthru.tests` did not pass.
- found 4.5.6 with grep in /nix/store/1l6gn0chzchfcmh9jamm5ani5r51s69g-blender-4.5.6
- found 4.5.6 in filename of file in /nix/store/1l6gn0chzchfcmh9jamm5ani5r51s69g-blender-4.5.6
---
Rebuild report (if merged into master) (click to expand)
```
5 total rebuild path(s)
5 package rebuild(s)
First fifty rebuilds by attrpath
blender
blendfarm
pkgsRocm.blender
pkgsRocm.blendfarm
```
Instructions to test this update (click to expand)
---
Either **download from the cache**:
```
nix-store -r /nix/store/1l6gn0chzchfcmh9jamm5ani5r51s69g-blender-4.5.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 blender https://github.com/r-ryantm/nixpkgs/archive/bfaf60fad17a25241c9e5db0bc47a05b49cbaa72.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/bfaf60fad17a25241c9e5db0bc47a05b49cbaa72#blender
```
After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/1l6gn0chzchfcmh9jamm5ani5r51s69g-blender-4.5.6
ls -la /nix/store/1l6gn0chzchfcmh9jamm5ani5r51s69g-blender-4.5.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: `bfaf60fad17a25241c9e5db0bc47a05b49cbaa72`
---
### `x86_64-linux`
:white_check_mark: 2 packages built:
---
###### Maintainer pings
cc @amarshall @veprbl 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/482004