sequoia-wot: init at 0.11.0

[Cryolitia]

Description of changes

https://gitlab.com/sequoia-pgp/sequoia-wot

A Rust library for authenticating bindings between User IDs and certificates using OpenPGP's web of trust. This library is designed around OpenPGP's data structures, but it does not require OpenPGP data. Instead, it is possible to manually describe a web of trust.

This crate also includes a CLI tool, sq-wot, for authenticating bindings and exploring a web of trust.

An official introduce article here: https://sequoia-pgp.org/blog/2023/03/29/202303-pretty-graphics-for-the-web-of-trust/

Thanks for review!

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.05 Release Notes (or backporting 23.05 and 23.11 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.

addressed

[doronbehar]

I saw this error on ofborg's Darwin build attempt:

tmp/nix-build-sequoia-wot-0.11.0.drv-0/source/target/x86_64-apple-darwin/release/deps/sq_wot_audit_data.o" "-Wl,-u,_AUDITABLE_VERSION_INFO"
  = note: ld: framework not found SystemConfiguration
          clang-16: error: linker command failed with exit code 1 (use -v to see invocation)

So I pushed an attempt to fix it.

[doronbehar]

I also removed libclang from the buildInputs, because it is not really required if you also include rustPlatform.bingenHook.

[doronbehar]

nix-init is pretty good at guessing buildInputs of rust packages apparently.

[Cryolitia]

Should I sign the commit and re-push? Or I could just waiting, doing nothing needed.

[doronbehar]

Should I sign the commit and re-push? Or I could just waiting, doing nothing needed.

I didn't mean to ask you to do anything, I only shared what I did, because it's hard to tell the difference with all of those force pushes. As for the signing, it is up to you - for Nixpkgs and for me it doesn't matter if you sign it or not. Force pushing now again will disrupt CI once more so consider that as well.

[Cryolitia]

Ok thx

[nbraud]

Looks good, OK to merge as far as I'm concerned, which I'll happily do once my question is answered

[doronbehar]

CI was completely green before, so I won't wait for darwin CI.

[doronbehar]

Thanks @Cryolitia for contributing this package 👍 .

[nbraud]

Thanks, @Cryolitia and @doronbehar :)