Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: emcee 0.7.0 -> 0.8.0 https://github.com/mattt/emcee/releases
attrpath: emcee
Checking auto update branch...
[version]
[version] generic version rewriter does not support multiple hashes
[rustCrateVersion]
[rustCrateVersion] No cargoHash found
[golangModuleVersion]
[golangModuleVersion] skipping because derivation has updateScript
[npmDepsVersion]
[npmDepsVersion] No npmDepsHash
[updateScript]
[updateScript] Success
[updateScript] this derivation will be built:
/nix/store/gqwrzmsdgajblbsib7y7kdlswv34zjqn-packages.json.drv
building '/nix/store/gqwrzmsdgajblbsib7y7kdlswv34zjqn-packages.json.drv'...
Going to be running update for following packages:
- emcee-0.7.0
Press Enter key to continue...
Running update for:
Enqueuing group of 1 packages
- emcee-0.7.0: UPDATING ...
- emcee-0.7.0: DONE.
Packages updated!
Diff after rewrites:
diff --git a/pkgs/by-name/em/emcee/package.nix b/pkgs/by-name/em/emcee/package.nix
index 1bc921e4fa5e..06c7bc02722d 100644
--- a/pkgs/by-name/em/emcee/package.nix
+++ b/pkgs/by-name/em/emcee/package.nix
@@ -8,13 +8,13 @@
buildGoModule (finalAttrs: {
pname = "emcee";
- version = "0.7.0";
+ version = "0.8.0";
src = fetchFromGitHub {
owner = "mattt";
repo = "emcee";
tag = "v${finalAttrs.version}";
- hash = "sha256-czOUhaPBxzuqZ72Y3TuzZ8r0Ab3OqGbDPZipkcak3Cw=";
+ hash = "sha256-S3hSexTjedfmjLuFHXtyiDiKM4NaLeUIJCEl2PKAOCw=";
};
vendorHash = "sha256-e8LPcKue7rhAh03uCRG0VTcwwyj3kDOBoeo3t7Hwvi0=";
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: `498e60d6708f46b1bdc1be4ae8c5798cef6e7dc7`
---
### `x86_64-linux`
: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 emcee is: Connect agents to APIs
meta.homepage for emcee is: https://github.com/mattt/emcee
meta.changelog for emcee is: https://github.com/mattt/emcee/releases/tag/v0.8.0
###### 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 0.8.0 with grep in /nix/store/lknfzlph1cdvkmp52dmrk2ih3i4xcprg-emcee-0.8.0
- found 0.8.0 in filename of file in /nix/store/lknfzlph1cdvkmp52dmrk2ih3i4xcprg-emcee-0.8.0
---
Rebuild report (if merged into master) (click to expand)
```
4 total rebuild path(s)
2 package rebuild(s)
First fifty rebuilds by attrpath
emcee
```
Instructions to test this update (click to expand)
---
Either **download from the cache**:
```
nix-store -r /nix/store/lknfzlph1cdvkmp52dmrk2ih3i4xcprg-emcee-0.8.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 emcee https://github.com/r-ryantm/nixpkgs/archive/498e60d6708f46b1bdc1be4ae8c5798cef6e7dc7.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/498e60d6708f46b1bdc1be4ae8c5798cef6e7dc7#emcee
```
After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/lknfzlph1cdvkmp52dmrk2ih3i4xcprg-emcee-0.8.0
ls -la /nix/store/lknfzlph1cdvkmp52dmrk2ih3i4xcprg-emcee-0.8.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: `498e60d6708f46b1bdc1be4ae8c5798cef6e7dc7`
---
### `x86_64-linux`
:white_check_mark: 1 package built:
---
###### Maintainer pings
cc @genga898 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/538545