Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: bilibili 1.18.0-1 -> 1.19.0-3 https://github.com/msojocs/bilibili-linux/releases
attrpath: bilibili
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/xfcggy2w91rlygavzk08108s117wgf7q-packages.json.drv
building '/nix/store/xfcggy2w91rlygavzk08108s117wgf7q-packages.json.drv'...
structuredAttrs is enabled
Going to be running update for following packages:
- bilibili-1.18.0-1
Press Enter key to continue...
Running update for:
Enqueuing group of 1 packages
- bilibili-1.18.0-1: UPDATING ...
- bilibili-1.18.0-1: DONE.
Packages updated!
Diff after rewrites:
diff --git a/pkgs/by-name/bi/bilibili/sources.nix b/pkgs/by-name/bi/bilibili/sources.nix
index fd7e312ada30..30d334bf8092 100644
--- a/pkgs/by-name/bi/bilibili/sources.nix
+++ b/pkgs/by-name/bi/bilibili/sources.nix
@@ -1,6 +1,6 @@
# Generated by ./update.sh - do not update manually!
{
- version = "1.18.0-1";
- arm64-hash = "sha256-DTBL11ikReCSXfdWjVd/noUQWq4OKKXP91jSZS/QCyo=";
- x86_64-hash = "sha256-EK0w3PwaNhGJhJZuTYBjpu+u6A3pb4V6zKji15ZeQwA=";
+ version = "1.19.0-3";
+ arm64-hash = "sha256-oM4KRhCJ5U2Hm0lQbDYHw1cAN2s5kPgOkP1N1+OVBtw=";
+ x86_64-hash = "sha256-ydDcF6SMZLT8TatR/WkGbhKwXPlo/CGChKYwMcHqCoE=";
}
An auto update branch exists with message `bilibili: 1.18.0-1 -> 1.19.0-1`. New version is 1.19.0-3.
The auto update branch does not match or exceed the new version.
Successfully finished processing
[check][nixpkgs-review]
[check][nixpkgs-review] took longer than 180m and timed out
:warning: nixpkgs-review took longer than 180m and timed out
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 bilibili is: Electron-based bilibili desktop client
meta.homepage for bilibili is: https://github.com/msojocs/bilibili-linux
###### Updates performed
- Ran passthru.UpdateScript
###### To inspect upstream changes
- [Compare changes on GitHub](https://github.com/msojocs/bilibili-linux/compare/v1.18.0-1...v1.19.0-3)
###### Impact
Checks done
---
- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 1.19.0-3 in filename of file in /nix/store/krhd4xvhvd23aabsi0spyjhhr273and9-bilibili-1.19.0-3
---
Rebuild report (if merged into master) (click to expand)
```
6 total rebuild path(s)
2 package rebuild(s)
First fifty rebuilds by attrpath
bilibili
```
Instructions to test this update (click to expand)
---
Either **download from the cache**:
```
nix-store -r /nix/store/krhd4xvhvd23aabsi0spyjhhr273and9-bilibili-1.19.0-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 bilibili https://github.com/r-ryantm/nixpkgs/archive/302b8818a3c32b4c506ca25742f944f1013c2212.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/302b8818a3c32b4c506ca25742f944f1013c2212#bilibili
```
After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/krhd4xvhvd23aabsi0spyjhhr273and9-bilibili-1.19.0-3
ls -la /nix/store/krhd4xvhvd23aabsi0spyjhhr273and9-bilibili-1.19.0-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.
:warning: nixpkgs-review took longer than 180m and timed out
---
###### Maintainer pings
cc @Jedsek @kashw2 @Bot-wxt1221 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).
Updated existing PR
https://api.github.com/repos/NixOS/nixpkgs/pulls/565774