Weekly nixpkgs update.

It looks like the only update this week is grafana, so assigning this to @florian for review.

nix store diff-closures

grafana: 7.5.10 → 7.5.11
nixos-system-monitoring: 21.05.3740.ce7a1190a0f → 21.05.3801.83667ff60a8
nixos-system-payments: 21.05.3740.ce7a1190a0f → 21.05.3801.83667ff60a8
nixos-system-storage001: 21.05.3740.ce7a1190a0f → 21.05.3801.83667ff60a8
nixos-system-storage002: 21.05.3740.ce7a1190a0f → 21.05.3801.83667ff60a8
nixos-system-storage003: 21.05.3740.ce7a1190a0f → 21.05.3801.83667ff60a8
nixos-system-storage004: 21.05.3740.ce7a1190a0f → 21.05.3801.83667ff60a8
nixos-system-storage005: 21.05.3740.ce7a1190a0f → 21.05.3801.83667ff60a8
nixos-system-storage1: 21.05.3740.ce7a1190a0f → 21.05.3801.83667ff60a8
nixos-system-storage2: 21.05.3740.ce7a1190a0f → 21.05.3801.83667ff60a8

Thanks!

I am generally for optimistically merging updates within a NixOS release (which should not break anything, right?) to develop - and if something breaks (because the release engineers at NixOs didn't do their job I guess?) we fix that breakage there, so we won't deploy the broken software to prod.

About only Grafana being updated: I don't understand why nixos-system-storage* and nixos-system-payments change too, but I am sure there is a reason for it. Maybe you can explain without going on a research safari?

From my point of view this update should add nothing, but with overhead maybe 10 MB to the VMs' used disk space. I'll be watching what happens since I feel our updates use much more space than is warranted (at least monitoring makes me think so).

approved this merge request

mentioned in commit c563f10f

merged

About only Grafana being updated: I don't understand why nixos-system-storage* and nixos-system-payments change too, but I am sure there is a reason for it. Maybe you can explain without going on a research safari?

I think that the nix diff store-closures output is only showing that the nixpkgs version number has changed for all of the nixos-system-* objects. Any of their content that changes needs to show up as a separate line of output, as the grafana change does.

Yes, exactly this. A NixOS system is itself a derivation, which by default has a version[1] that corresponds to the nixos channel version used (though it can be overridden by nixos.label or nixos.version).

[1] Derivations versions are a little weird in nix. At the concrete level, the name is split at the first -not followed by a letter, and everything after that is the version. That is the version shown by diff-closures above. At the nix expression level, a derivation can have a version attribute; conventionally it has both a pname and version attribute, and the name is {pname}-{version}, but given that everything as strings, the combine string may end up being split differently by the concrete layer.

changed the description

mentioned in merge request !210 (merged)

mentioned in merge request !228 (merged)