text:
failed to run matrix-synapse tests

Issue description
When I execute the tests I get trapped in a strange endless loop that I'm failing to debug, which is repeatedly trying to start the synapse service all over the place.
I have this problem for quite a while now, see e.g. #41036 , #39922, #39285
It seems like the script is trying to get the matrix-synapse service up forever, but fails to realize the service is already up. The synapse log messages in between show that synapse is actually running. restart counter slowly increases after some timeout, I guess, which makes the whole process take ages until it gives up.
I can reproduce this on my virtual servers as well as on real hardware, with synapse running and without, but found no one else so far who can reproduce. @GrahamcOfBorg has no issues. I have no idea what could cause this, sadly. :(
Snippet of one loop iteration:
[…]
server_postgres# [ 1036.015450] systemd[1]: Starting Synapse Matrix homeserver...
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_sqlite# [ 1040.019706] synapse[738]: synapse.storage.event_push_actions: [None] Searching for stream ordering 1 month ago
server_sqlite# [ 1040.069995] synapse[738]: synapse.storage.event_push_actions: [None] Found stream ordering 1 month ago: it's 0
server_sqlite# [ 1040.097636] synapse[738]: synapse.storage.event_push_actions: [None] Searching for stream ordering 1 day ago
server_sqlite# [ 1040.133412] synapse[738]: synapse.storage.event_push_actions: [None] Found stream ordering 1 day ago: it's 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_sqlite# [ 1040.787431] synapse[738]: synapse.handlers.presence: [] Performing _persist_unpersisted_changes. Persisting 0 unpersisted changes
server_sqlite# [ 1040.805846] synapse[738]: synapse.handlers.presence: [] Finished _persist_unpersisted_changes
server_sqlite# [ 1040.830466] synapse[738]: synapse.handlers.typing: [] Checking for typing timeouts
server_sqlite# [ 1040.852232] synapse[738]: synapse.handlers.presence: [] Handling presence timeouts
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_sqlite# [ 1042.623694] synapse[738]: synapse.storage: [None] Calling _generate_user_daily_visits
server_sqlite# [ 1042.714606] synapse[738]: synapse.storage.TIME: [] Total database time: 2.073% {_find_stream_orderings_for_times(1): 1.514%, generate_user_daily_visits(1): 0.444%, update_cached_last_access_time(1): 0.090%} {}
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_sqlite# [ 1045.847477] synapse[738]: synapse.handlers.typing: [] Checking for typing timeouts
server_sqlite# [ 1045.892926] synapse[738]: synapse.handlers.presence: [] Handling presence timeouts
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_sqlite# [ 1050.822498] synapse[738]: synapse.handlers.typing: [] Checking for typing timeouts
server_sqlite# [ 1050.845697] synapse[738]: synapse.handlers.presence: [] Handling presence timeouts
server_postgres: exit status 0
server_sqlite# [ 1052.734240] synapse[738]: synapse.storage.TIME: [] Total database time: 0.082% {_update_client_ips_batch(2): 0.082%, update_user_directory_stream_pos(0): 0.000%, update_cached_last_access_time(0): 0.000%} {}
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_sqlite# [ 1055.846723] synapse[738]: synapse.handlers.typing: [] Checking for typing timeouts
server_sqlite# [ 1055.867798] synapse[738]: synapse.handlers.presence: [] Handling presence timeouts
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_sqlite# [ 1060.820435] synapse[738]: synapse.handlers.typing: [] Checking for typing timeouts
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_sqlite# [ 1060.838952] synapse[738]: synapse.handlers.presence: [] Handling presence timeouts
server_postgres: exit status 0
server_sqlite# [ 1062.729605] synapse[738]: synapse.storage.TIME: [] Total database time: 0.027% {_update_client_ips_batch(2): 0.027%, update_user_directory_stream_pos(0): 0.000%, update_cached_last_access_time(0): 0.000%} {}
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_sqlite# [ 1065.819618] synapse[738]: synapse.handlers.typing: [] Checking for typing timeouts
server_sqlite# [ 1065.842841] synapse[738]: synapse.handlers.presence: [] Handling presence timeouts
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_sqlite# [ 1070.838723] synapse[738]: synapse.handlers.typing: [] Checking for typing timeouts
server_sqlite# [ 1070.887859] synapse[738]: synapse.handlers.presence: [] Handling presence timeouts
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_sqlite# [ 1072.735809] synapse[738]: synapse.storage.TIME: [] Total database time: 0.041% {_update_client_ips_batch(2): 0.041%, update_user_directory_stream_pos(0): 0.000%, update_cached_last_access_time(0): 0.000%} {}
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_sqlite# [ 1075.807426] synapse[738]: synapse.handlers.typing: [] Checking for typing timeouts
server_sqlite# [ 1075.824505] synapse[738]: synapse.handlers.presence: [] Handling presence timeouts
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_sqlite# [ 1080.813720] synapse[738]: synapse.handlers.typing: [] Checking for typing timeouts
server_sqlite# [ 1080.834503] synapse[738]: synapse.handlers.presence: [] Handling presence timeouts
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_sqlite# [ 1082.721554] synapse[738]: synapse.storage.TIME: [] Total database time: 0.078% {_update_client_ips_batch(2): 0.078%, update_user_directory_stream_pos(0): 0.000%, update_cached_last_access_time(0): 0.000%} {}
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_sqlite# [ 1085.850836] synapse[738]: synapse.handlers.typing: [] Checking for typing timeouts
server_sqlite# [ 1085.904921] synapse[738]: synapse.handlers.presence: [] Handling presence timeouts
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_sqlite# [ 1090.797852] synapse[738]: synapse.handlers.typing: [] Checking for typing timeouts
server_sqlite# [ 1090.816604] synapse[738]: synapse.handlers.presence: [] Handling presence timeouts
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_sqlite# [ 1092.726981] synapse[738]: synapse.storage.TIME: [] Total database time: 0.077% {_update_client_ips_batch(2): 0.077%, update_user_directory_stream_pos(0): 0.000%, update_cached_last_access_time(0): 0.000%} {}
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_sqlite# [ 1095.805641] synapse[738]: synapse.handlers.typing: [] Checking for typing timeouts
server_sqlite# [ 1095.828238] synapse[738]: synapse.handlers.presence: [] Handling presence timeouts
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_sqlite# [ 1100.808709] synapse[738]: synapse.handlers.presence: [] Performing _persist_unpersisted_changes. Persisting 0 unpersisted changes
server_sqlite# [ 1100.855940] synapse[738]: synapse.handlers.presence: [] Finished _persist_unpersisted_changes
server_sqlite# [ 1100.892616] synapse[738]: synapse.handlers.typing: [] Checking for typing timeouts
server_sqlite# [ 1100.914005] synapse[738]: synapse.handlers.presence: [] Handling presence timeouts
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_sqlite# [ 1102.724667] synapse[738]: synapse.storage.TIME: [] Total database time: 0.086% {update_cached_last_access_time(1): 0.063%, _update_client_ips_batch(2): 0.023%, update_user_directory_stream_pos(0): 0.000%} {}
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_sqlite# [ 1105.835894] synapse[738]: synapse.handlers.typing: [] Checking for typing timeouts
server_sqlite# [ 1105.864186] synapse[738]: synapse.handlers.presence: [] Handling presence timeouts
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_sqlite# [ 1110.818986] synapse[738]: synapse.handlers.typing: [] Checking for typing timeouts
server_sqlite# [ 1110.853021] synapse[738]: synapse.handlers.presence: [] Handling presence timeouts
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_sqlite# [ 1112.789518] synapse[738]: synapse.storage.TIME: [] Total database time: 0.050% {_update_client_ips_batch(2): 0.050%, update_user_directory_stream_pos(0): 0.000%, update_cached_last_access_time(0): 0.000%} {}
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_sqlite# [ 1115.814575] synapse[738]: synapse.handlers.typing: [] Checking for typing timeouts
server_sqlite# [ 1115.837672] synapse[738]: synapse.handlers.presence: [] Handling presence timeouts
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_sqlite# [ 1120.804552] synapse[738]: synapse.handlers.typing: [] Checking for typing timeouts
server_sqlite# [ 1120.822203] synapse[738]: synapse.handlers.presence: [] Handling presence timeouts
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_sqlite# [ 1122.727985] synapse[738]: synapse.storage.TIME: [] Total database time: 0.043% {_update_client_ips_batch(2): 0.043%, update_user_directory_stream_pos(0): 0.000%, update_cached_last_access_time(0): 0.000%} {}
server_postgres: exit status 0
server_postgres# [ 1123.661644] sudo[1568]:     root : TTY=unknown ; PWD=/var/lib/matrix-synapse ; USER=postgres ; COMMAND=/nix/store/gnj95a4hip3mrnnk9p14lx0h1di37a4k-postgresql-9.6.8/bin/createuser --login --no-createdb --no-createrole --encrypted matrix-synapse
server_postgres# [ 1123.828680] sudo[1568]: pam_unix(sudo:session): session opened for user postgres by (uid=0)
server_postgres# [ 1123.904753] matrix-synapse-pre-start[1517]: createuser: could not connect to database postgres: could not connect to server: No such file or directory
server_postgres# [ 1123.933783] matrix-synapse-pre-start[1517]:         Is the server running locally and accepting
server_postgres# [ 1123.944904] matrix-synapse-pre-start[1517]:         connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
server_postgres# [ 1123.959608] sudo[1568]: pam_unix(sudo:session): session closed for user postgres
server_postgres# [ 1123.993224] systemd[1]: matrix-synapse.service: Control process exited, code=exited status=1
server_postgres# [ 1124.020703] systemd[1]: matrix-synapse.service: Failed with result 'exit-code'.
server_postgres# [ 1124.086258] systemd[1]: Failed to start Synapse Matrix homeserver.
server_postgres# [ 1124.284496] systemd[1]: matrix-synapse.service: Service hold-off time over, scheduling restart.
server_postgres# [ 1124.300282] systemd[1]: matrix-synapse.service: Scheduled restart job, restart counter is at 8.
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres# [ 1124.323244] systemd[1]: Stopped Synapse Matrix homeserver.
server_postgres# [ 1124.485864] systemd[1]: Starting Synapse Matrix homeserver...
server_sqlite# [ 1125.800734] synapse[738]: synapse.handlers.typing: [] Checking for typing timeouts
server_sqlite# [ 1125.818981] synapse[738]: synapse.handlers.presence: [] Handling presence timeouts
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
server_sqlite# [ 1130.800833] synapse[738]: synapse.handlers.typing: [] Checking for typing timeouts
server_sqlite# [ 1130.818547] synapse[738]: synapse.handlers.presence: [] Handling presence timeouts
server_postgres: running command: systemctl --no-pager show "matrix-synapse.service"
server_postgres: exit status 0
[…]

Maintainer: @corngood
Steps to reproduce
cd nixpkgs/nixos/test
nix-build matrix-synapse.nix

Technical details

system: "x86_64-linux"
host os: Linux 4.15.18, NixOS, 18.03.132448.33682d9af4c (Impala)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 2.0.2
channels(root): "nixos-18.03, nixos-unstable-18.09pre139651.6db7f92cc2a"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

I cannot reproduce this on my local machine. Test runs fine on ofborg as well. Maybe a timing issue/race condition. Will try to make the test more robust.

@xeji thanks! Let me know if I can help out with something.

@florianjacob is this still the case as of 18.09?

Can't reproduce with current master. I guess matrix-synapse 0.99 / the switch to python3 made synapse fast enough so that even on my old machines, the race condition doesn't show up anymore.

authors: aanderse florianjacob xeji


text:
Vulnerability roundup 51: libtiff-4.0.9

libtiff-4.0.9: 3 advisories
search, files

[ ] CVE-2018-17000 (unstable, 18.09, 18.03)
[ ] CVE-2018-17100 (unstable, 18.09, 18.03)
[ ] CVE-2018-17101 (unstable, 18.09, 18.03)

libtiff-4.0.10 has been released @andrew-d

obsolete: 19.03 ships libtiff-4.0.10

source: gharchive/issue

repo: NixOS/nixpkgs

license: MIT

license_type: permissive

license_source: github-api


text:
libreoffice 6.2 supports qt5/kde

Issue description
Would be great if LO could be compiled with plasma integration
https://wiki.documentfoundation.org/ReleaseNotes/6.2#KDE_5_.2B_Qt5
Cc: @7c6f434c

I do not object, but cannot easily test it so probably I won't investigate it myself.

Fixed with the introduction of libreoffice-qt.


text:
Vulnerability roundup 89: xrdp-0.9.9: 1 advisory [7.8]

search, files

[ ] CVE-2020-4044 CVSSv3=7.8 (nixos-20.03, nixos-unstable)

Scanned versions: nixos-20.03: dabbc5a5603; nixos-unstable: c71518e75bf. May contain false positives.
Cc @volth

Fixed by #209509

authors: FliegendeWurst ckauhaus


text:
sshuttle: 0.61 -> 0.71

Account for a zany new build system & add myself as a maintainer.
Tested by connecting to a remote system and browsing the web & LAN,
both as root and a regular (sudo) user. Cool tool. Will use a lot.
CC @iElectric

Since GitHub probably won't ping on edits:  @domenkozar.

source: gharchive/pull-request


text:
[20.09] GNOME polishing from Q.A findings

Motivation for this change
backports #101516
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

planning to merge very soon as I don't want to release without it


text:
ocamlPackages.digestif: 0.8.0 → 0.9.0

Motivation for this change
SHA3: https://github.com/mirage/digestif/releases/tag/v0.9.0
Use Dune 2.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build ocamlPackages.irmin-unix


text:
oprofile: depend on kernel headers to correctly compile 'operf' util.

For 'operf' utility to be built linux kernel headers dependency should be added.
This is my first commit here, so please help me to be correct.

I've copied the dependency logic from glibc package. There is the same overriding. Why should I create something different?
OK. I'll create another commit...

overriding :smile:

The glibc expression would benefit from some refactoring, after all those years.

authors: tk-ecotelecom vcunat


text:
python3Packages.coapthon3: init at 1.0.1

Motivation for this change
The coapthon3 Python package is not yet packaged.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after) init at 452.2K
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 104528 run on x86_64-linux 1

3 packages built:

python27Packages.coapthon3
python37Packages.coapthon3
python38Packages.coapthon3

Result of nixpkgs-review pr 104528 run on x86_64-darwin 1

3 packages built:

python27Packages.coapthon3
python37Packages.coapthon3
python38Packages.coapthon3


text:
mavproxy: 1.8.24 -> 1.8.27

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for mavproxy is: "MAVLink proxy and command line ground station"
meta.homepage for mavproxy is: "https://github.com/ArduPilot/MAVProxy"
meta.changelog for mavproxy is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.8.27 with grep in /nix/store/cwli23sjj22js4jjx6gg221dcyr7m6fx-MAVProxy-1.8.27

directory tree listing: https://gist.github.com/ddbb62c6e1bb038dca6dd1a6fa8f32ff

du listing: https://gist.github.com/711e53a35e74e703c4659e01e3132d9a

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

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
mavproxy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/cwli23sjj22js4jjx6gg221dcyr7m6fx-MAVProxy-1.8.27 \
  --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 mavproxy https://github.com/r-ryantm/nixpkgs/archive/3174ae1723f4eb6d249e88ff4fd02ef816b8b134.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/cwli23sjj22js4jjx6gg221dcyr7m6fx-MAVProxy-1.8.27
ls -la /nix/store/cwli23sjj22js4jjx6gg221dcyr7m6fx-MAVProxy-1.8.27/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 1

1 package built:

mavproxy

Maintainer pings
cc @lopsided98 for testing.

Result of nixpkgs-review pr 104866 run on x86_64-darwin 1

1 package marked as broken and skipped:

mavproxy


text:
perlPackages.ParallelPipes: init at 0.005

Motivation for this change
https://metacpan.org/release/Parallel-Pipes
Dependency for App::cpm
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[X] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 104975 run on x86_64-linux 1

2 packages built:

perl530Packages.ParallelPipes
perl532Packages.ParallelPipes

Result of nixpkgs-review pr 104975 run on x86_64-darwin 1

2 packages built:

perl530Packages.ParallelPipes
perl532Packages.ParallelPipes

Thanks @stigtsp @SuperSandro2000 ! :tada:


text:
fly: 6.7.0 -> 6.7.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/fly/versions.
meta.description for fly is: "A command line interface to Concourse CI"
meta.homepage for fly is: "https://concourse-ci.org"
meta.changelog for fly is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 6.7.2 with grep in /nix/store/ffncr0xxvdhbkr8ay8biimvssi12wr3d-fly-6.7.2

directory tree listing: https://gist.github.com/c885b4ce6cbf43290b87af5ff1f53c0e

du listing: https://gist.github.com/0c9f230bbb514a0fd5e7c52fe345fd7d

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

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
fly

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ffncr0xxvdhbkr8ay8biimvssi12wr3d-fly-6.7.2 \
  --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 fly https://github.com/r-ryantm/nixpkgs/archive/1590c5302baae3f9deece67b859f877e329c89a9.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ffncr0xxvdhbkr8ay8biimvssi12wr3d-fly-6.7.2
ls -la /nix/store/ffncr0xxvdhbkr8ay8biimvssi12wr3d-fly-6.7.2/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 1

1 package built:

fly

Maintainer pings
cc @ivanbrennan @kalbasit for testing.

Result of nixpkgs-review pr 105607 run on x86_64-darwin 1

1 package built:

fly


text:
[20.09] nixUnstable: patch #4470 (ETag) (#111005)

Co-authored-by: Jörg Thalheim Mic92@users.noreply.github.com
(cherry picked from commit 1d41739764af5e7d280fb8efc1f5eac4e01ef2a2)

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Evaluates correctly, but ofborg hasn't started on the darwin build after many hours. The patch isn't os-specific, so I see no reason for it to fail. Probably best to merge anyway.

Evaluates correctly, but ofborg hasn't started on the darwin build after many hours. The patch isn't os-specific, so I see no reason for it to fail. Probably best to merge anyway.

Evaluates correctly, but ofborg hasn't started on the darwin build after many hours. The patch isn't os-specific, so I see no reason for it to fail. Probably best to merge anyway.

We don't have a darwin builder for quite a while.

Evaluates correctly, but ofborg hasn't started on the darwin build after many hours. The patch isn't os-specific, so I see no reason for it to fail. Probably best to merge anyway.

We don't have a darwin builder for quite a while.


text:
ecl: 20.4.24 -> 21.2.1, enable Darwin

Motivation for this change

Incorporates the latest upstream release
Removes now-defunct patches
Enable builds on non-Linux Unixes, ie. Darwin

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
- No, could not be built locally previously. Looks reasonable though, given that it includes gcc.
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Seems to break maxima-ecl, at least on Darwin: nix-shell -p nixpkgs-review --run "nixpkgs-review wip" says
error: --- Error ------------------------------------------------------------------------------------------------- nix
while setting up the build environment: getting attributes of path '/usr/lib/libSystem.B.dylib': No such file or directory
1 package failed to build:
maxima-ecl

Result of nixpkgs-review pr 112718 at 8628c902 run on aarch64-linux 1

3 packages built:

ecl
eql
maxima-ecl

Result of nixpkgs-review pr 112718 at 8628c902 run on x86_64-linux 1

2 packages failed to build:

sage
sageWithDoc

3 packages built:

ecl
eql
maxima-ecl

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 112718 run on x86_64-darwin 1

2 packages built:

ecl
maxima-ecl

authors: SuperSandro2000 purcell r-rmcgibbo


text:
nixos/nextcloud: fix regex to not return 404 on ACME challenges

Motivation for this change
Fixes #113027
cc @sjau
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Ported to stable as 3d7db4e82cc4a7ed9e78e48d01878873c2ea78f1.


text:
ldeep: 1.0.10 -> 1.0.11

Motivation for this change
Update to latest upstream release 1.0.11
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 119985 run on x86_64-linux 1

1 package built:

ldeep


text:
python3Packages.growattserver: init at 1.0.1

Motivation for this change
Python package to retrieve information from Growatt units
https://github.com/indykoning/PyPi_GrowattServer
This is a Home Assistant dependency.

Related Home Assistant change: https://github.com/home-assistant/core/pull/41303
Target Home Assistant release: 2021.6.0

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 123179 at 9ca996cf run on aarch64-linux 1

1 package failed to build:

home-assistant

2 packages built successfully:

python38Packages.growattserver
python39Packages.growattserver

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

@fabaff please resolve the merge conflict.

I have cherry-picked this change into my staging tree, thank you!

authors: SuperSandro2000 fabaff mweinelt r-rmcgibbo


text:
gpg-tui: 0.5.0 -> 0.6.0

Motivation for this change
https://github.com/orhun/gpg-tui/blob/v0.6.0/CHANGELOG.md
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 128149 run on x86_64-linux 1

1 package built:

gpg-tui

authors: dotlambda fabaff


text:
dnsproxy: 0.37.7 -> 0.38.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/AdguardTeam/dnsproxy/releases.
meta.description for dnsproxy is: "Simple DNS proxy with DoH, DoT, and DNSCrypt support"
meta.homepage for dnsproxy is: "https://github.com/AdguardTeam/dnsproxy"
meta.changelog for dnsproxy is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/imbk1vpv237sq2y38k1f786ydxg9rbrs-dnsproxy-0.38.0/bin/dnsproxy passed the binary check.

1 of 1 passed binary check by having a zero exit code.

0 of 1 passed binary check by having the new version present in output.

found 0.38.0 with grep in /nix/store/imbk1vpv237sq2y38k1f786ydxg9rbrs-dnsproxy-0.38.0

found 0.38.0 in filename of file in /nix/store/imbk1vpv237sq2y38k1f786ydxg9rbrs-dnsproxy-0.38.0

directory tree listing: https://gist.github.com/045a02f2090849e3ad3858d2a159ce95

du listing: https://gist.github.com/7ebde33b42561fd01d83797f1bcf8a22

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

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
dnsproxy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/imbk1vpv237sq2y38k1f786ydxg9rbrs-dnsproxy-0.38.0 \
  --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 dnsproxy https://github.com/r-ryantm/nixpkgs/archive/31257ffdc3c3fa52afc683c342f173e9bb03d085.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/imbk1vpv237sq2y38k1f786ydxg9rbrs-dnsproxy-0.38.0
ls -la /nix/store/imbk1vpv237sq2y38k1f786ydxg9rbrs-dnsproxy-0.38.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.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

dnsproxy

Maintainer pings
cc @contrun @kalbasit for testing.

Result of nixpkgs-review pr 128200 at 31257ffd run on aarch64-linux 1

1 package built successfully:

dnsproxy

1 suggestion:

warning: unclear-gpl
gpl3 is a deprecated license, please check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/tools/networking/dnsproxy/default.nix:21:5:
   |
21 |     license = licenses.gpl3;
   |     ^

authors: r-rmcgibbo r-ryantm


text:
python3Packages.trezor: fix build by easing click dependency

Motivation for this change

fix build after breakage caused by updating click to 8.x
https://github.com/NixOS/nixpkgs/pull/127151#issuecomment-869788446

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Duplicate of https://github.com/NixOS/nixpkgs/pull/128530


text:
python38Packages.yamllint: 1.26.2 -> 1.26.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.yamllint is: "A linter for YAML files"
meta.homepage for python38Packages.yamllint is: "https://github.com/adrienverge/yamllint"
meta.changelog for python38Packages.yamllint is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

/nix/store/v8j3pcvjd1zjglra8hdl1grbn520d4f4-python3.8-yamllint-1.26.3/bin/yamllint passed the binary check.

/nix/store/v8j3pcvjd1zjglra8hdl1grbn520d4f4-python3.8-yamllint-1.26.3/bin/.yamllint-wrapped passed the binary check.

2 of 2 passed binary check by having a zero exit code.

2 of 2 passed binary check by having the new version present in output.

found 1.26.3 with grep in /nix/store/v8j3pcvjd1zjglra8hdl1grbn520d4f4-python3.8-yamllint-1.26.3

found 1.26.3 in filename of file in /nix/store/v8j3pcvjd1zjglra8hdl1grbn520d4f4-python3.8-yamllint-1.26.3

directory tree listing: https://gist.github.com/8e7d3faee57bb62328d1fa3dc8cda3e5

du listing: https://gist.github.com/e90869dbd2ab606a88e9294827430095

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

42 total rebuild path(s)

11 package rebuild(s)

11 x86_64-linux rebuild(s)
10 i686-linux rebuild(s)
11 x86_64-darwin rebuild(s)
10 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
ansible-lint
fdroidserver
python38Packages.ansible-lint
python38Packages.junos-eznc
python38Packages.ntc-templates
python38Packages.yamllint
python39Packages.ansible-lint
python39Packages.junos-eznc
python39Packages.ntc-templates
python39Packages.yamllint
yamllint

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/v8j3pcvjd1zjglra8hdl1grbn520d4f4-python3.8-yamllint-1.26.3 \
  --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 python38Packages.yamllint https://github.com/r-ryantm/nixpkgs/archive/0e7b7bc224d5a1db10006f6b40b801f8b629e659.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/v8j3pcvjd1zjglra8hdl1grbn520d4f4-python3.8-yamllint-1.26.3
ls -la /nix/store/v8j3pcvjd1zjglra8hdl1grbn520d4f4-python3.8-yamllint-1.26.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.
Result of nixpkgs-review run on x86_64-linux 1

9 packages built:

ansible-lint (python39Packages.ansible-lint)
fdroidserver
python38Packages.ansible-lint
python38Packages.junos-eznc
python38Packages.ntc-templates
python38Packages.yamllint
python39Packages.junos-eznc
python39Packages.ntc-templates
yamllint (python39Packages.yamllint)

Maintainer pings
cc @jonringer @mikefaille for testing.

Result of nixpkgs-review pr 135180 at 0e7b7bc2 run on aarch64-linux 1

8 packages built successfully:

ansible-lint (python39Packages.ansible-lint)
python38Packages.ansible-lint
python38Packages.junos-eznc
python38Packages.ntc-templates
python38Packages.yamllint
python39Packages.junos-eznc
python39Packages.ntc-templates
yamllint (python39Packages.yamllint)


text:
tidy-viewer: 1.4.2 -> 1.4.3

Motivation for this change
https://github.com/alexhallam/tv/compare/1.4.2...1.4.3
https://github.com/alexhallam/tv/blob/main/CHANGELOG.md
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 146438 run on x86_64-linux 1

1 package built:

tidy-viewer

authors: figsoda thiagokokada


text:
nixpkgs-review: 2.6.3 -> 2.6.4

Motivation for this change
This release fixes aarch64-darwin support by always using local eval instead of relying on ofborg's eval output.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

waiting for someone on aarch64-darwin to test/merge.


text:
Rust Updates

Various Rust and Cargo updates.
rustc updated to 1.8.0
cargo updated to 0.9.0 (we can't update to 0.10.0, as it breaks our buildRustPackage function https://github.com/NixOS/nixpkgs/issues/11144#issuecomment-212079455) and enabled Darwin compatibility.
rustfmt updated to 0.4.0
heatseeker updated to 1.4.0
exa updated to 2016-04-20 to fix compilation with rustc 1.8.0
pijul now using stable rustPlatform
Added myself as maintainer for rustc and cargo.
Should fix: https://github.com/NixOS/nixpkgs/issues/10864
@vcunat I enabled parallel building for rustc, which you disabled here: https://github.com/NixOS/nixpkgs/commit/d7e87db0c7f8d0ed759261cdfbdd2c71a7933bf0. If those errors return - we could disable it again, but it builds okay on my NixOS and Darwin machines.
Rust head fails test suite on Mac OS X due net errors. I will investigate this later as rust stable compiles and runs okay.

[x] Tested using sandboxing (nix-build --option build-use-chroot true or nix.useChroot on NixOS)
Built on platform(s)

[x] NixOS
[x] OS X
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@abbradar (ok to ping you about rust stuff? The other mentions aren't actively reviewing, and I don't have permissions to merge)

@jgillich It's OK -- I have a personal interest in Rust.
Left this to test-build and going to sleep; I'll merge in ~8 hours if it succeeds unless someone is faster.

enableParallelBuilding: well, you should get e-mails from Hydra if it fails again...

authors: abbradar jgillich retrry vcunat


text:
python3Packages.subzerod: init at 1.0

Motivation for this change
Python module to help with the enumeration of subdomains
https://github.com/sanderfoobar/subzerod
Related to #81418
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 150033 run on x86_64-linux 1

2 packages built:

python38Packages.subzerod
subzerod (python39Packages.subzerod)


text:
networkmanager_dmenu: 1.6.0 -> 2.1.0

Motivation for this change
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

packaging looks ok but the software itself might be a bit buggy. trying to change wifi network triggers issues
.cache/nixpkgs-review/pr-157342 via ❄  IMPURE (review-shell) took 20s
(ins)❯ results/networkmanager_dmenu/bin/networkmanager_dmenu

(process:927675): XrmOptions-WARNING **: 10:54:21.948: Option: columns is not found.

(process:927675): XrmOptions-WARNING **: 10:54:21.948: Option: width is not found.
Segmentation fault (core dumped)
.cache/nixpkgs-review/pr-157342 via ❄  IMPURE (review-shell) took 2s
(ins)❯ results/networkmanager_dmenu/bin/networkmanager_dmenu

(process:927992): XrmOptions-WARNING **: 10:54:28.573: Option: columns is not found.

(process:927992): XrmOptions-WARNING **: 10:54:28.573: Option: width is not found.
Traceback (most recent call last):
  File "/nix/store/jmrmyxcd6fivh9rc0asxkbw8n006s32c-networkmanager_dmenu-2.0.1/bin/.networkmanager_dmenu-wrapped", line 879, in <module>
    run()
  File "/nix/store/jmrmyxcd6fivh9rc0asxkbw8n006s32c-networkmanager_dmenu-2.0.1/bin/.networkmanager_dmenu-wrapped", line 875, in run
    sel()
  File "/nix/store/jmrmyxcd6fivh9rc0asxkbw8n006s32c-networkmanager_dmenu-2.0.1/bin/.networkmanager_dmenu-wrapped", line 264, in __call__
    self.func(*self.args)
  File "/nix/store/jmrmyxcd6fivh9rc0asxkbw8n006s32c-networkmanager_dmenu-2.0.1/bin/.networkmanager_dmenu-wrapped", line 298, in process_ap
    CLIENT.deactivate_connection_async(nm_ap, None, deactivate_cb, nm_ap)
TypeError: Argument 1 does not allow None as a value
Segmentation fault (core dumped)

@teto

packaging looks ok but the software itself might be a bit buggy. trying to change wifi network triggers issues

They changed the config format and that might be causing these issues.
Compare your ~/.config/networkmanager-dmenu/config.ini to the included $out/share/config.ini.example to see what I mean.

Is this ready to be merged?

As far as I'm concerned: yes.

Is this backportable to 22.05 or does this stay unstable till 22.11?

yes if the version on stable is broken, no otherwise I think.

authors: Lyndeno magnetophon teto


text:
nixos-rebuild: add --no-flake switch

When a NixOS system uses flakes, i.e., /etc/nixos/flake.nix exists, it is impossible to use nixos-rebuild to build a pre-flake configuration.nix. Of course, one can directly use nix command to build the configuration, but not everybody remembers the correct nix options to do that.
With the new option, it is possible to build a pre-flake configuration with command like this:
nixos-rebuild build-vm -I nixos-config=./vm.nix --no-flake

The option might be useful for people following older pre-flake tutorials on a flake-based system.

Motivation for this change
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Seems to work:
> ./result/bin/nixos-rebuild test
building the system configuration...
error: experimental Nix feature 'nix-command' is disabled; use '--extra-experimental-features nix-command' to override
> ./result/bin/nixos-rebuild test --no-flake
building Nix...
^Cerror (ignored): error: interrupted by the user

(after touching /etc/nixos/flake.nix)

authors: Profpatsch wentasah


text:
treewide: cleanup old throw aliases

Description of changes
Delete throws older than 2020-01-01

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

/marvin opt-in
/status needs_reviewer

checked that the removed aliases are indeed as old as they claim. :+1:

@fabianhjr please rebase and give me a ping to merge.

Hi @SuperSandro2000, the conflict has been resolved and this PR has been rebased.

@jonringer anything we need to take care of before?

added an only-throws option to the remove-old-aliases script https://github.com/NixOS/nixpkgs/pull/165971

@jonringer anything we need to take care of before?

nope, this looks good to me

authors: Artturin SuperSandro2000 fabianhjr jonringer pennae


text:
pipenv: 2022.4.8 -> 2022.4.21

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for pipenv is: "Python Development Workflow for Humans"
meta.homepage for pipenv is: ""
meta.changelog for pipenv is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2022.4.21 with grep in /nix/store/hhzv60a08xkra67h2vgygm5s206k739q-pipenv-2022.4.21
found 2022.4.21 in filename of file in /nix/store/hhzv60a08xkra67h2vgygm5s206k739q-pipenv-2022.4.21

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

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
pipenv

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hhzv60a08xkra67h2vgygm5s206k739q-pipenv-2022.4.21 \
  --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 pipenv https://github.com/r-ryantm/nixpkgs/archive/eb43857314eb5b2bbec455abd053f10a5b5479d9.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hhzv60a08xkra67h2vgygm5s206k739q-pipenv-2022.4.21
ls -la /nix/store/hhzv60a08xkra67h2vgygm5s206k739q-pipenv-2022.4.21/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 run on x86_64-linux 1

1 package built:

pipenv

Maintainer pings
cc @berdario for testing.

Result of nixpkgs-review pr 169880 run on x86_64-linux 1

1 package built:

pipenv

Superseded by #178326

authors: arjan-s r-ryantm smancill


text:
esptool: 3.3.1 -> 4.2.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for esptool is: "ESP8266 and ESP32 serial bootloader utility"
meta.homepage for esptool is: "https://github.com/espressif/esptool"
meta.changelog for esptool is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.1 with grep in /nix/store/260azyy0m9jh2s8fbvv5i05azh7nx86b-esptool-4.1
found 4.1 in filename of file in /nix/store/260azyy0m9jh2s8fbvv5i05azh7nx86b-esptool-4.1

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

3 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
esphome
esptool

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/260azyy0m9jh2s8fbvv5i05azh7nx86b-esptool-4.1 \
  --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 esptool https://github.com/r-ryantm/nixpkgs/archive/af5bf3b560d5f5c70025c732c1e15d443acf77ce.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/260azyy0m9jh2s8fbvv5i05azh7nx86b-esptool-4.1
ls -la /nix/store/260azyy0m9jh2s8fbvv5i05azh7nx86b-esptool-4.1/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 run on x86_64-linux 1

2 packages built:

esphome
esptool

Maintainer pings
cc @dezgeg @dotlambda for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for esptool is: "ESP8266 and ESP32 serial bootloader utility"
meta.homepage for esptool is: "https://github.com/espressif/esptool"
meta.changelog for esptool is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.2.1 with grep in /nix/store/iqm86hnh0rdhcqg6f6ns5hm54npp5884-esptool-4.2.1
found 4.2.1 in filename of file in /nix/store/iqm86hnh0rdhcqg6f6ns5hm54npp5884-esptool-4.2.1

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
esphome
esptool

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/iqm86hnh0rdhcqg6f6ns5hm54npp5884-esptool-4.2.1 \
  --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 esptool https://github.com/r-ryantm/nixpkgs/archive/fdfe4ce5d34dabc087d227270366c11ea0e70f5e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/iqm86hnh0rdhcqg6f6ns5hm54npp5884-esptool-4.2.1
ls -la /nix/store/iqm86hnh0rdhcqg6f6ns5hm54npp5884-esptool-4.2.1/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 run on x86_64-linux 1

2 packages built:

esphome
esptool

Maintainer pings
cc @dezgeg @dotlambda @roelvandijk @Lucus16 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for esptool is: "ESP8266 and ESP32 serial bootloader utility"
meta.homepage for esptool is: "https://github.com/espressif/esptool"
meta.changelog for esptool is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.3 with grep in /nix/store/9d144dsfxc4w70swsm4b618fy1rrj1wh-esptool-4.3
found 4.3 in filename of file in /nix/store/9d144dsfxc4w70swsm4b618fy1rrj1wh-esptool-4.3

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
esphome
esptool

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9d144dsfxc4w70swsm4b618fy1rrj1wh-esptool-4.3 \
  --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 esptool https://github.com/r-ryantm/nixpkgs/archive/42536cb020af2777527211ae78bd0dcad8dc5e32.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9d144dsfxc4w70swsm4b618fy1rrj1wh-esptool-4.3
ls -la /nix/store/9d144dsfxc4w70swsm4b618fy1rrj1wh-esptool-4.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.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

esphome
esptool

Maintainer pings
cc @dezgeg @dotlambda @roelvandijk @Lucus16 for testing.


text:
python310Packages.google-cloud-storage: 2.2.1 -> 2.3.0

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 175823 run on x86_64-linux 1

47 packages built:

dvc-with-remotes
python310Packages.gcsfs
python310Packages.gensim
python310Packages.google-cloud-automl
python310Packages.google-cloud-bigquery
python310Packages.google-cloud-bigtable
python310Packages.google-cloud-core
python310Packages.google-cloud-datastore
python310Packages.google-cloud-dns
python310Packages.google-cloud-error-reporting
python310Packages.google-cloud-firestore
python310Packages.google-cloud-logging
python310Packages.google-cloud-resource-manager
python310Packages.google-cloud-runtimeconfig
python310Packages.google-cloud-spanner
python310Packages.google-cloud-storage
python310Packages.google-cloud-trace
python310Packages.google-cloud-translate
python310Packages.pathy
python310Packages.smart-open
python310Packages.spacy
python310Packages.spacy-transformers
python310Packages.textacy
python39Packages.gcsfs
python39Packages.gensim
python39Packages.google-cloud-automl
python39Packages.google-cloud-bigquery
python39Packages.google-cloud-bigtable
python39Packages.google-cloud-core
python39Packages.google-cloud-datastore
python39Packages.google-cloud-dns
python39Packages.google-cloud-error-reporting
python39Packages.google-cloud-firestore
python39Packages.google-cloud-logging
python39Packages.google-cloud-resource-manager
python39Packages.google-cloud-runtimeconfig
python39Packages.google-cloud-spanner
python39Packages.google-cloud-storage
python39Packages.google-cloud-trace
python39Packages.google-cloud-translate
python39Packages.pathy
python39Packages.smart-open
python39Packages.spacy
python39Packages.spacy-transformers
python39Packages.textacy
snakemake
wal_e


text:
bazel-remote: 2.3.7 -> 2.3.8

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/buchgr/bazel-remote/releases.
meta.description for bazel-remote is: "A remote HTTP/1.1 cache for Bazel"
meta.homepage for bazel-remote is: "https://github.com/buchgr/bazel-remote"
meta.changelog for bazel-remote is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.3.8 with grep in /nix/store/gj4k1vh7z9x17nfyjlkprq68nammyjl4-bazel-remote-2.3.8
found 2.3.8 in filename of file in /nix/store/gj4k1vh7z9x17nfyjlkprq68nammyjl4-bazel-remote-2.3.8

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

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
bazel-remote

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gj4k1vh7z9x17nfyjlkprq68nammyjl4-bazel-remote-2.3.8 \
  --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 bazel-remote https://github.com/r-ryantm/nixpkgs/archive/4a706341b1697868373f4ca717d2974f8541f84b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gj4k1vh7z9x17nfyjlkprq68nammyjl4-bazel-remote-2.3.8
ls -la /nix/store/gj4k1vh7z9x17nfyjlkprq68nammyjl4-bazel-remote-2.3.8/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 run on x86_64-linux 1

1 package built:

bazel-remote

Maintainer pings
cc @mboes @marsam @uri-canva @avdv @olebedev @groodt @aherrmann @ylecornec @kalbasit for testing.

Result of nixpkgs-review pr 180617 run on x86_64-linux 1

1 package built:

bazel-remote

authors: avdv r-ryantm