Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: osmium 0 -> 1
attrpath: osmium
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/3wrxcb36m4nn2w3hnqa2apnj9dlybhmi-packages.json.drv
building '/nix/store/3wrxcb36m4nn2w3hnqa2apnj9dlybhmi-packages.json.drv'...
Going to be running update for following packages:
- osmium-0.0.30-alpha
Press Enter key to continue...
Running update for:
Enqueuing group of 1 packages
- osmium-0.0.30-alpha: UPDATING ...
- osmium-0.0.30-alpha: DONE.
Packages updated!
Diff after rewrites:
diff --git a/pkgs/by-name/os/osmium/package.nix b/pkgs/by-name/os/osmium/package.nix
index bbd5040f3061..4a1ec4f33ba9 100644
--- a/pkgs/by-name/os/osmium/package.nix
+++ b/pkgs/by-name/os/osmium/package.nix
@@ -29,11 +29,11 @@
stdenv.mkDerivation rec {
pname = "osmium";
- version = "0.0.30-alpha";
+ version = "0.0.32-alpha";
src = fetchurl {
url = "https://updater.osmium.chat/Osmium-${version}-x64.tar.gz";
- hash = "sha256-NF7RF8odDQfh4zhk5B4md4OqDgh538exFNsRZzSJwBM=";
+ hash = "sha256-gW8AuO1W2MesYPgmXji8INyXKMXeP85+8MgieEn/UHo=";
};
nativeBuildInputs = [
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: `f75fb4a1bf24e7e5191754d8fdb242120d91aea8`
---
### `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 osmium is: Globally distributed community messaging and voice/video platform
meta.homepage for osmium is: https://osmium.chat/
###### 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.0.32-alpha with grep in /nix/store/fnkaqfy29rrk8qwzqd1p20bmy037qzq9-osmium-0.0.32-alpha
- found 0.0.32-alpha in filename of file in /nix/store/fnkaqfy29rrk8qwzqd1p20bmy037qzq9-osmium-0.0.32-alpha
---
Rebuild report (if merged into master) (click to expand)
```
4 total rebuild path(s)
2 package rebuild(s)
First fifty rebuilds by attrpath
osmium
```
Instructions to test this update (click to expand)
---
Either **download from the cache**:
```
nix-store -r /nix/store/fnkaqfy29rrk8qwzqd1p20bmy037qzq9-osmium-0.0.32-alpha \
--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 osmium https://github.com/r-ryantm/nixpkgs/archive/f75fb4a1bf24e7e5191754d8fdb242120d91aea8.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/f75fb4a1bf24e7e5191754d8fdb242120d91aea8#osmium
```
After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/fnkaqfy29rrk8qwzqd1p20bmy037qzq9-osmium-0.0.32-alpha
ls -la /nix/store/fnkaqfy29rrk8qwzqd1p20bmy037qzq9-osmium-0.0.32-alpha/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: `f75fb4a1bf24e7e5191754d8fdb242120d91aea8`
---
### `x86_64-linux`
:white_check_mark: 1 package built:
---
###### Maintainer pings
cc @twoneis 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/546805