tigervnc: 1.15.0 -> 1.16.0

[r-ryantm]

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/tigervnc/versions.

meta.description for tigervnc is: Fork of tightVNC, made in cooperation with VirtualGL

meta.homepage for tigervnc is: https://tigervnc.org/

Updates performed

• Version update

To inspect upstream changes

Impact

Checks done

---

• built on NixOS
• The tests defined in passthru.tests, if any, passed
• found 1.16.0 with grep in /nix/store/vr22jp0505h0ssifbgx53dyq2sj5sim2-tigervnc-1.16.0
• found 1.16.0 in filename of file in /nix/store/vr22jp0505h0ssifbgx53dyq2sj5sim2-tigervnc-1.16.0

---

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

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath

crowbar
nemu
tigervnc

Instructions to test this update (click to expand)

---

Either download from the cache:

nix-store -r /nix/store/vr22jp0505h0ssifbgx53dyq2sj5sim2-tigervnc-1.16.0 \
  --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 tigervnc https://github.com/r-ryantm/nixpkgs/archive/340d3540c0954d122f648a5ca3e72035d7dac20a.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/340d3540c0954d122f648a5ca3e72035d7dac20a#tigervnc

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

ls -la /nix/store/vr22jp0505h0ssifbgx53dyq2sj5sim2-tigervnc-1.16.0
ls -la /nix/store/vr22jp0505h0ssifbgx53dyq2sj5sim2-tigervnc-1.16.0/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: 340d3540c0954d122f648a5ca3e72035d7dac20a

---

x86_64-linux

✅ 4 packages built:

• crowbar
• crowbar.dist
• nemu
• tigervnc

---

Maintainer pings

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.