nixVersions.nix_2_25: init at 2.25.2

[zowoq]

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• 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/)
• 24.11 Release Notes (or backporting 23.11 and 24.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
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[Mic92]

Things that need to be tested:

• nixpkgs-review on x86_64-linux
• nixpkgs-review on x86_64-darwin
• nixpkgs-review on aarch64-linux
• nixpkgs-review on aarch64-darwin
• passthru.tests
• Furthermore fallback-paths.nix needs to be updated (check update-all.sh or the README for how to do this.

I can probably run most of the reviews later on.

[Mic92]

I would suggest to split the PR into two. First one just adds 2.25 and the second one does the actual switch. If in the future it turns out that the switch goes smoothly we can upgrade nix right away.

[zowoq]

I would suggest to split the PR into two. First one just adds 2.25 and the second one does the actual switch.

nixVersions.latest: 2.24 -> 2.25

You want the latest bump moved to another PR?

[Mic92]

You want the latest bump moved to another PR?

Yes I think this would speed up the process a bit.

[lovesegfault]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 355350

---

x86_64-linux

❌ 5 packages failed to build:

• nixVersions.nix_2_25
• nixVersions.nix_2_25.debug
• nixVersions.nix_2_25.dev
• nixVersions.nix_2_25.doc
• nixVersions.nix_2_25.man

[lovesegfault]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 355350

---

aarch64-linux

❌ 5 packages failed to build:

• nixVersions.nix_2_25
• nixVersions.nix_2_25.debug
• nixVersions.nix_2_25.dev
• nixVersions.nix_2_25.doc
• nixVersions.nix_2_25.man

[lovesegfault]

It'd be nice if we started leveraging the new meson build system, I think, but that can happen in another PR as well

[lovesegfault]

Both failures are due to tests/functional/ca/repl.sh failing, and retrying does not seem to help.

[lovesegfault]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 355350

---

aarch64-darwin

✅ 4 packages built:

• nixVersions.nix_2_25
• nixVersions.nix_2_25.dev
• nixVersions.nix_2_25.doc
• nixVersions.nix_2_25.man

[Mic92]

It'd be nice if we started leveraging the new meson build system, I think, but that can happen in another PR as well

That's a bit more involved. @roberth has something for it in the works.