Gabriel de Perthuis

I think the issue is with the Rust release key itself, which uses SHA-1 digests: gpg --list-packets --verbose < src/rust-key.pgp.ascii |grep digest.algo algo 2 is SHA-1: https://datatracker.ietf.org/doc/html/rfc4880#section-9.4 Should switch to...

Apparently it is possible to update the digest algorithms without changing the key-id: https://gitlab.com/sequoia-pgp/keyring-linter Although it might be good to consider key rotation support later, to future-proof against any other...

Just as a heads-up, I've been working on my own on adding missing features within ocaml-interop. The most polished branches are for bigarrays and passing Rust types to OCaml through...

I have worked as much as I can on this pre-rooting changes, and will have a look at porting to these changes after that. I'm pretty sure the change to...

I'm sending PRs for trivial stuff, and I'll hold on the rest (though, the branches are published) until you tell me it's fine to base work on your changes.

There's a PR for get_key_value at #35. I couldn't do insert_key_value, getting a key with the map lifetime from hash_map::Entry can't be done in one go / without cloning, see...

I've started prototyping, here's the help output: -F, --fixed-strings Treat the pattern as a literal string instead of a regular expression. Note that the pattern would still match on a...

globset would need to be patched, however, as anchoring is always done inside Token::to_regex_with with no builder customisation. But since globs are written by hand and still easy to script...

Addresses #297. Ideally this would be tested in CI.

Build failure with rust 1.60 is unrelated; the following runs fine: cargo +nightly update -Zminimal-versions cargo +1.60 check --all-features