[Backport release-24.11] dotnet: migrate nuget lockfiles to JSON

[corngood]

Backport of #362278

I've removed all conflicting packages from the treewide commit.

Cc: @NixOS/dotnet

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/)
• 25.05 Release Notes (or backporting 24.11 and 25.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.

[corngood]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 366269

---

x86_64-linux

⏩ 1 package blacklisted:

• nixos-install-tools

✅ 3 packages built:

• nixpkgs-manual
• nuget-to-json
• nuget-to-nix

[MattSturgeon]

I've removed all conflicting packages from the treewide commit.

Would it be reasonable to re-generate json lockfiles for those packages too, and amend the treewide commit?

✅ 3 packages built:

Had me worried there was an eval difference, but of course it is the infrastructure packages that are actually supposed to be different.

[corngood]

Would it be reasonable to re-generate json lockfiles for those packages too, and amend the treewide commit?

I sort of don't think it's worth the effort, because it's mostly due to packages that have already made changes that weren't backported. If someone wants to do it though, I have no problem with that.

[MattSturgeon]

Would it be reasonable to re-generate json lockfiles for those packages too, and amend the treewide commit?

I sort of don't think it's worth the effort, because it's mostly due to packages that have already made changes that weren't backported.

That's fair.

If someone wants to do it though, I have no problem with that.

If so, probably best to use @GGG-KILLER's script: migrate-nuget.sh

[GGG-KILLER]

If possible I think it'd be better to migrate all lockfiles to JSON to make it easier on people who want to backport changes after our treewide on master.

If you'd like I could do that on another PR since I don't have write perms to your branch.

[corngood]

@GGG-KILLER I can always pull your change here if you share it somewhere

[GGG-KILLER]

@corngood I've pushed my changes to https://github.com/GGG-KILLER/nixpkgs/tree/backport-362278-to-release-24.11

I haven't added any changes from #366556 nor #366574 because they're still under review.

[corngood]

@GGG-KILLER I grabbed your branch, plus those two fixes. Let me know what you think. Thanks for doing the rest of the conversions.

[MattSturgeon]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 366269

---

x86_64-linux

⏩ 1 package blacklisted:

• nixos-install-tools

✅ 3 packages built:

• nixpkgs-manual
• nuget-to-json
• nuget-to-nix

[GGG-KILLER]

Looks good to me!