Etienne Millon

Hmm, I might be mistaken. According to some docs, the signature is part of the mach-o file. It's in a xattr just for non-mach-o binaries. So there might be something...

I now have access to a M1 machine. I fixed a couple issues and now the main testsuite is passing! There are still issues with the fsevents tests but they're...

> Can you disabile them from `dune test` or document what to run on M1? One hacky way of doing that is by running `CI=true make test`. I'd like to...

Regarding reproducibility of code signing: my understanding is that ad-hoc signatures are not signatures in the cryptographic sense - they only record a hash of the data that would be...

The fsevent thing is unrelated, I'll open a new issue (edit: it's #6151).

According to the description in #5120, that's intentional. This warning only happens when the package is defined in `dune-project`. So I don't think it's a bug or a regression (has...

2 different things: - I agree that the feature needs some tests - we can extend the behavior to packages defined through an opam file For the latter, the "classic"...

I'll add tests (first part of the above) but the for second part, I'm not sure how to proceed: if we add a warning for packages that are defined through...

In addition, while writing tests I noticed that the warning case can never happen. I'll fix that next week.

I can work on this since we require this for mirage.