firecracker: 1.9.1 -> 1.10.1

[usertam]

Simple version update and I reworked the aws-lc-sys deps. Should be less hacky than the last.

Hopefully using rustPlatform.fetchCargoVendor will make auto-updates easier. I see it is already in nix-update?

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.

[usertam]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 373359

---

x86_64-linux

✅ 2 packages built:

• firecracker
• flintlock

[techknowlogick]

Thanks @usertam, could you nixfmt this as well?

[usertam]

Thanks @usertam, could you nixfmt this as well?

It will turn

cargoTestFlags = [ "--package" "firecracker" "--package" "jailer" ];

into

cargoTestFlags = [
  "--package"
  "firecracker"
  "--package"
  "jailer"
];

which looks kinda off... 😬 Do I still do it?

[techknowlogick]

which looks kinda off... 😬 Do I still do it?

I agree, it doesn't look the best. I'm not sure if passing nixfmt is mandatory at this point, so if it isn't, then leaving as-is is probably fine.

Either way, this bump/your changes work pass my testing too, so I'll give this a +1 from me, and await feedback from someone who knows more about nixfmt requirements.