Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: darkly 0.5.32 -> 0.5.36 https://github.com/Bali10050/Darkly/releases
attrpath: darkly
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]
Going to be running update for following packages:
- darkly-qt6-0.5.32
Press Enter key to continue...
Running update for:
Enqueuing group of 1 packages
- darkly-qt6-0.5.32: UPDATING ...
- darkly-qt6-0.5.32: DONE.
Packages updated!
Diff after rewrites:
diff --git a/pkgs/by-name/da/darkly/package.nix b/pkgs/by-name/da/darkly/package.nix
index 9a8ddb9f439f..8bcc4e0ea42a 100644
--- a/pkgs/by-name/da/darkly/package.nix
+++ b/pkgs/by-name/da/darkly/package.nix
@@ -13,13 +13,13 @@ let
in
stdenv.mkDerivation (finalAttrs: {
pname = "darkly-qt${qtMajorVersion}";
- version = "0.5.32";
+ version = "0.5.36";
src = fetchFromGitHub {
owner = "Bali10050";
repo = "Darkly";
tag = "v${finalAttrs.version}";
- hash = "sha256-bW0untIUe6QMygBPABCMyrnaZCo8E4pKRQGZgLO9aGI=";
+ hash = "sha256-ugmR2mQ2YSQ8fatFMpPND7I2pMv0xIZq170cogWC9P0=";
};
nativeBuildInputs = [
An auto update branch exists with message `darkly: 0.5.32 -> 0.5.34`. New version is 0.5.36.
The auto update branch does not match or exceed the new version.
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: `6cea8ddc8a7ac5bffa8445543847aa1ad4f3a3db`
---
### `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 darkly is: Modern style for Qt applications (fork of Lightly)
meta.homepage for darkly is: https://github.com/Bali10050/Darkly
meta.changelog for darkly is: https://github.com/Bali10050/Darkly/releases/tag/v0.5.36
###### 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.5.36 with grep in /nix/store/4g9hxhcp8py3q94bwlnvpyrx9kjgq77x-darkly-qt6-0.5.36
- found 0.5.36 in filename of file in /nix/store/4g9hxhcp8py3q94bwlnvpyrx9kjgq77x-darkly-qt6-0.5.36
---
Rebuild report (if merged into master) (click to expand)
```
3 total rebuild path(s)
3 package rebuild(s)
First fifty rebuilds by attrpath
darkly
darkly-qt5
```
Instructions to test this update (click to expand)
---
Either **download from the cache**:
```
nix-store -r /nix/store/4g9hxhcp8py3q94bwlnvpyrx9kjgq77x-darkly-qt6-0.5.36 \
--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 darkly https://github.com/r-ryantm/nixpkgs/archive/6cea8ddc8a7ac5bffa8445543847aa1ad4f3a3db.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/6cea8ddc8a7ac5bffa8445543847aa1ad4f3a3db#darkly
```
After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/4g9hxhcp8py3q94bwlnvpyrx9kjgq77x-darkly-qt6-0.5.36
ls -la /nix/store/4g9hxhcp8py3q94bwlnvpyrx9kjgq77x-darkly-qt6-0.5.36/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: `6cea8ddc8a7ac5bffa8445543847aa1ad4f3a3db`
---
### `x86_64-linux`
:white_check_mark: 2 packages built:
---
###### Maintainer pings
cc @pluiedev 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/498133