hydrus: 675 -> 676 by r-ryantm · Pull Request #515005 · NixOS/nixpkgs

r-ryantm · 2026-04-30T08:44:23Z

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

meta.description for hydrus is: Danbooru-like image tagging and searching system for the desktop

meta.homepage for hydrus is: https://hydrusnetwork.github.io/hydrus/

meta.changelog for hydrus is: https://github.com/hydrusnetwork/hydrus/releases/tag/v670

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 670 with grep in /nix/store/5kzsc5d7jq3k3qc3zs8anfwcnkhkndv6-hydrus-670
found 670 in filename of file in /nix/store/5kzsc5d7jq3k3qc3zs8anfwcnkhkndv6-hydrus-670

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

hydrus

Instructions to test this update (click to expand)

Either download from the cache:

nix-store -r /nix/store/5kzsc5d7jq3k3qc3zs8anfwcnkhkndv6-hydrus-670 \
  --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 hydrus https://github.com/r-ryantm/nixpkgs/archive/decf6117c7fe2a5b14d859409194eb0ec153dd38.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/decf6117c7fe2a5b14d859409194eb0ec153dd38#hydrus

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/5kzsc5d7jq3k3qc3zs8anfwcnkhkndv6-hydrus-670
ls -la /nix/store/5kzsc5d7jq3k3qc3zs8anfwcnkhkndv6-hydrus-670/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.

Command: nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'
Commit: decf6117c7fe2a5b14d859409194eb0ec153dd38

`x86_64-linux`

✅ 2 packages built:

hydrus
hydrus.doc

Maintainer pings

cc @D4ndellion @evanjs @KunyaKud for testing.

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.

r-ryantm · 2026-05-25T05:56:41Z

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

meta.description for hydrus is: Danbooru-like image tagging and searching system for the desktop

meta.homepage for hydrus is: https://hydrusnetwork.github.io/hydrus/

meta.changelog for hydrus is: https://github.com/hydrusnetwork/hydrus/releases/tag/v672

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 672 with grep in /nix/store/898pvxidfcag8cr203ipz8n8kcy8chzj-hydrus-672
found 672 in filename of file in /nix/store/898pvxidfcag8cr203ipz8n8kcy8chzj-hydrus-672

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

hydrus

Instructions to test this update (click to expand)

Either download from the cache:

nix-store -r /nix/store/898pvxidfcag8cr203ipz8n8kcy8chzj-hydrus-672 \
  --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 hydrus https://github.com/r-ryantm/nixpkgs/archive/c876b9fed1eac7e71b8296863f986a694f688a26.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/c876b9fed1eac7e71b8296863f986a694f688a26#hydrus

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/898pvxidfcag8cr203ipz8n8kcy8chzj-hydrus-672
ls -la /nix/store/898pvxidfcag8cr203ipz8n8kcy8chzj-hydrus-672/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.

Command: nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'
Commit: c876b9fed1eac7e71b8296863f986a694f688a26

`x86_64-linux`

✅ 1 package built:

hydrus

Maintainer pings

cc @D4ndellion @evanjs @KunyaKud for testing.

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.

r-ryantm · 2026-06-29T19:55:21Z

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

meta.description for hydrus is: Danbooru-like image tagging and searching system for the desktop

meta.homepage for hydrus is: https://hydrusnetwork.github.io/hydrus/

meta.changelog for hydrus is: https://github.com/hydrusnetwork/hydrus/releases/tag/v676

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 676 with grep in /nix/store/s3fh4yfkrw4jmh9naxlz74b310f3ib1i-hydrus-676
found 676 in filename of file in /nix/store/s3fh4yfkrw4jmh9naxlz74b310f3ib1i-hydrus-676

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

hydrus

Instructions to test this update (click to expand)

Either download from the cache:

nix-store -r /nix/store/s3fh4yfkrw4jmh9naxlz74b310f3ib1i-hydrus-676 \
  --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 hydrus https://github.com/r-ryantm/nixpkgs/archive/2d316ee5f33089bab1c2723f1362b4af3ec13261.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/2d316ee5f33089bab1c2723f1362b4af3ec13261#hydrus

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/s3fh4yfkrw4jmh9naxlz74b310f3ib1i-hydrus-676
ls -la /nix/store/s3fh4yfkrw4jmh9naxlz74b310f3ib1i-hydrus-676/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.

Command: nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'
Commit: 2d316ee5f33089bab1c2723f1362b4af3ec13261

`x86_64-linux`

✅ 1 package built:

hydrus

Maintainer pings

cc @D4ndellion @evanjs @KunyaKud for testing.

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.

nixpkgs-ci Bot requested review from D4ndellion, KunyaKud and evanjs April 30, 2026 08:50

r-ryantm changed the title ~~hydrus: 668 -> 670~~ hydrus: 668 -> 672 May 25, 2026

r-ryantm force-pushed the auto-update/hydrus branch from decf611 to c876b9f Compare May 25, 2026 05:56

hydrus: 675 -> 676

2d316ee

r-ryantm changed the title ~~hydrus: 668 -> 672~~ hydrus: 675 -> 676 Jun 29, 2026

r-ryantm force-pushed the auto-update/hydrus branch from c876b9f to 2d316ee Compare June 29, 2026 19:55

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

hydrus: 675 -> 676#515005

hydrus: 675 -> 676#515005
r-ryantm wants to merge 1 commit into
NixOS:masterfrom
r-ryantm:auto-update/hydrus

r-ryantm commented Apr 30, 2026

Uh oh!

r-ryantm commented May 25, 2026

Uh oh!

r-ryantm commented Jun 29, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Uh oh!

Conversation

r-ryantm commented Apr 30, 2026

Updates performed

To inspect upstream changes

Impact

Pre-merge build results

nixpkgs-review result

x86_64-linux

Maintainer pings

Uh oh!

r-ryantm commented May 25, 2026

Updates performed

To inspect upstream changes

Impact

Pre-merge build results

nixpkgs-review result

x86_64-linux

Maintainer pings

Uh oh!

r-ryantm commented Jun 29, 2026

Updates performed

To inspect upstream changes

Impact

Pre-merge build results

nixpkgs-review result

x86_64-linux

Maintainer pings

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

`nixpkgs-review` result

`x86_64-linux`

`nixpkgs-review` result

`x86_64-linux`

`nixpkgs-review` result

`x86_64-linux`