makejinja: 2.6.2 -> 2.7.2

[mirkolenz]

• Update makejinja to v2.7.2
• Switch build-system to setuptools (makejinja switched from poetry to uv starting with v2.7.0)
• Use tag instead of rev for fetching the sources

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.

[lucasewd]

nixpkgs-reviewd workflow started

Status and logs: https://github.com/nixosbrasil/nixpkgs-reviewd/actions/runs/12474044145

[lucasewd]

nixpkgs-reviewd workflow finished

Status and logs: https://github.com/nixosbrasil/nixpkgs-reviewd/actions/runs/12474044145

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 367762

---

x86_64-darwin

✅ 2 packages built:

• makejinja
• makejinja.dist

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 367762

---

aarch64-darwin

✅ 2 packages built:

• makejinja
• makejinja.dist

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 367762

---

x86_64-linux

✅ 2 packages built:

• makejinja
• makejinja.dist

[TomaSajt]

LGTM

A small improvement would be to add a meta.changelog field to the derivation

[mirkolenz]

Yeah, makes sense. Should I use the GitHub releases page as the changelog?

[TomaSajt]

Yeah, makes sense. Should I use the GitHub releases page as the changelog?

I think the usual was it's done is that you use the changelog file if possible and fall back to the release page if that's not present.

In this case, since there's a changelog file, you'd use this:
https://github.com/mirkolenz/makejinja/blob/${src.rev}/CHANGELOG.md