openocd-unstable: init at 0.12.0-unstable-2026-06-11

[mkannwischer]

Things done

• Built on platform:
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• Tested, as applicable:
  • NixOS tests in nixos/tests.
  • Package tests at passthru.tests.
  • Tests in lib/tests or pkgs/test for functions and "core" functionality.
• Ran nixpkgs-review on this PR. See nixpkgs-review usage.
• Tested basic functionality of all binary files, usually in ./result/bin/.
• Nixpkgs Release Notes
  • Package update: when the change is major or breaking.
• NixOS Release Notes
  • Module addition: when adding a new NixOS module.
  • Module update: when the change is significant.
• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.
• Follows the automation/AI policy.

[mkannwischer]

@bjornfor @prusnak, do you mind if we add an unstable version of openocd in addition to the stable 0.12.0?
We need support for STM32N6 target in mlkem-native (see this PR) and I would prefer not having to build it from source every time.

[mkannwischer]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 531668
Commit: 02b90f3b1cea95bc06989f4c7b70fc514324a5a6

---

aarch64-darwin

✅ 1 package built:

• openocd-unstable

[bjornfor]

@bjornfor @prusnak, do you mind if we add an unstable version of openocd in addition to the stable 0.12.0? We need support for STM32N6 target in mlkem-native (see this PR) and I would prefer not having to build it from source every time.

My preference is to not do that. I won't object to it, but I prefer to spend my time on other things.

Why not nudge/help upstream to make a release rather than maintain a package that require more frequent updates, and also has a higher risk of getting stale?

[prusnak]

Why not nudge/help upstream to make a release rather than maintain a package that require more frequent updates, and also has a higher risk of getting stale?

I agree with nudging upstream to make a new release makes more sense.

In the meantime you can have a look at https://www.cachix.org to set up your Nix cache, so you do not have to rebuild from source every time.

[SuperSandro2000]

If it would be in tree, we could talk about it but since it is for out of tree we should not accept this PR.