r-ryantm
commented
1 day ago Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for zrok is: Geo-scale, next-generation sharing platform built on top of OpenZiti
meta.homepage for zrok is: https://zrok.io
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.4.32 with grep in /nix/store/86dy2z8299yy8lm6b5r8fr3brgjsh0zy-zrok-0.4.32
- found 0.4.32 in filename of file in /nix/store/86dy2z8299yy8lm6b5r8fr3brgjsh0zy-zrok-0.4.32
Rebuild report (if merged into master) (click to expand)
``` 2 total rebuild path(s) 2 package rebuild(s) First fifty rebuilds by attrpath zrok ```Instructions to test this update (click to expand)
--- Either **download from Cachix**: ``` nix-store -r /nix/store/86dy2z8299yy8lm6b5r8fr3brgjsh0zy-zrok-0.4.32 \ --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \ --option trusted-public-keys ' nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs= cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY= ' ``` (The Cachix cache is only trusted for this store-path realization.) For the Cachix 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 zrok https://github.com/r-ryantm/nixpkgs/archive/2db825d1a88814f48405dfff7143e836e95f6717.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/2db825d1a88814f48405dfff7143e836e95f6717#zrok ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/86dy2z8299yy8lm6b5r8fr3brgjsh0zy-zrok-0.4.32 ls -la /nix/store/86dy2z8299yy8lm6b5r8fr3brgjsh0zy-zrok-0.4.32/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.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1
1 package built:
- zrok
Maintainer pings
cc @bennyandresen for testing.
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for zrok is: Geo-scale, next-generation sharing platform built on top of OpenZiti
meta.homepage for zrok is: https://zrok.io
Updates performed
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
Impact
Checks done
passthru.tests, if any, passedRebuild report (if merged into master) (click to expand)
``` 2 total rebuild path(s) 2 package rebuild(s) First fifty rebuilds by attrpath zrok ```Instructions to test this update (click to expand)
--- Either **download from Cachix**: ``` nix-store -r /nix/store/rad1mnsmga6v3aly3imkw0jr18js95i6-zrok-0.4.31 \ --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \ --option trusted-public-keys ' nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs= cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY= ' ``` (The Cachix cache is only trusted for this store-path realization.) For the Cachix 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 zrok https://github.com/r-ryantm/nixpkgs/archive/65b4a4a940fbe97c65f9cf9b6e6c31b9f3c7c93f.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/65b4a4a940fbe97c65f9cf9b6e6c31b9f3c7c93f#zrok ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/rad1mnsmga6v3aly3imkw0jr18js95i6-zrok-0.4.31 ls -la /nix/store/rad1mnsmga6v3aly3imkw0jr18js95i6-zrok-0.4.31/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.
Result of
nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }'run on x86_64-linux 11 package built:
Maintainer pings
cc @bennyandresen for testing.