Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: beeper 0 -> 1 attrpath: beeper 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] these 2 derivations will be built: /nix/store/s918pf5jaj2yxl8gvbhj53by1w7ir0qg-update-beeper.drv /nix/store/pqi7pklqvkp3c9l5rnrydv61isp98wqy-packages.json.drv building '/nix/store/s918pf5jaj2yxl8gvbhj53by1w7ir0qg-update-beeper.drv'... building '/nix/store/pqi7pklqvkp3c9l5rnrydv61isp98wqy-packages.json.drv'... Going to be running update for following packages: - beeper-4.2.532 Press Enter key to continue... Running update for: Enqueuing group of 1 packages - beeper-4.2.532: UPDATING ... - beeper-4.2.532: DONE. Packages updated! Diff after rewrites: diff --git a/pkgs/by-name/be/beeper/package.nix b/pkgs/by-name/be/beeper/package.nix index 2e9cf71d09c7..4d30cc8113e4 100644 --- a/pkgs/by-name/be/beeper/package.nix +++ b/pkgs/by-name/be/beeper/package.nix @@ -9,10 +9,10 @@ }: let pname = "beeper"; - version = "4.2.532"; + version = "4.2.547"; src = fetchurl { url = "https://beeper-desktop.download.beeper.com/builds/Beeper-${version}-x86_64.AppImage"; - hash = "sha256-7v3MPwfsW47rP8Nnt39M9aBR4niYEaG2UZ6cuMfVp+Q="; + hash = "sha256-PuthmxdIuftaK9U9r52Fc9b8JzYPwxezRhWjdyo+nmA="; }; appimageContents = appimageTools.extract { inherit pname version src; 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: `edc1fa21a30d4dbb8e15c84315aa327fde429425` --- ### `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 beeper is: Universal chat app meta.homepage for beeper is: https://beeper.com ###### 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 4.2.547 with grep in /nix/store/sjxka93lzj7h6azj6339vzrch98myj7f-beeper-4.2.547 - found 4.2.547 in filename of file in /nix/store/sjxka93lzj7h6azj6339vzrch98myj7f-beeper-4.2.547 ---
Rebuild report (if merged into master) (click to expand) ``` 2 total rebuild path(s) 2 package rebuild(s) First fifty rebuilds by attrpath beeper ```
Instructions to test this update (click to expand) --- Either **download from the cache**: ``` nix-store -r /nix/store/sjxka93lzj7h6azj6339vzrch98myj7f-beeper-4.2.547 \ --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 beeper https://github.com/r-ryantm/nixpkgs/archive/edc1fa21a30d4dbb8e15c84315aa327fde429425.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/edc1fa21a30d4dbb8e15c84315aa327fde429425#beeper ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/sjxka93lzj7h6azj6339vzrch98myj7f-beeper-4.2.547 ls -la /nix/store/sjxka93lzj7h6azj6339vzrch98myj7f-beeper-4.2.547/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: `edc1fa21a30d4dbb8e15c84315aa327fde429425` --- ### `x86_64-linux`
:white_check_mark: 1 package built:
--- ###### Maintainer pings cc @jshcmpbll @zh4ngx 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/489626