Document situations where not pinning the nix version changes outputs

[nh2]

In

static-haskell-nix/static-stack2nix-builder-example/default.nix

Line 36 in d24dea3

# Full invocation, including pinning `nix` version itself.

I pin the version of nix itself.

I added that in the past because the upgrade from Nix 1.* to 2.0 created (if I remember correctly) different .drv files.

I would like to document cases beyond that which resulted in different .drvs or build outputs when the version of nix changes, so that I can justify to continue pinning nix:

.drv changes

• During the ugprade from nix 1.* to 2.0

Output / build changes

• Python unicode errors: pythonPackages.Babel: Fix use of glibcLocales, skip musl tests NixOS/nixpkgs#75676 (comment)

[nh2]

I found another situation:

NixOS/nixpkgs#75676 (comment)

From Nix 2.2 to 2.3, nix changed to run its builds in a TTY (PR: NixOS/nix#2878) which can easily result in different build behaviour e.g. for Python:

Before, we'd get

('sys.stdout.encoding', None)
('sys.stdout.isatty()', False)

and afterwards we'd get

('sys.stdout.encoding', 'UTF-8')
('sys.stdout.isatty()', True)

and some code inspects that; in the linked case it led to a test failure in python2Packages.Babel.