1these 3 derivations will be built:2 /nix/store/f2349v6lw5v7xahs3nav81wyl6vwynxy-integration-proton-authcmd.drv3 /nix/store/fqpsmxp9p3yz8zhzfr6q9akxq32w7jcw-python3-3.14.6-env.drv4 /nix/store/yvmgn4qlsglqlc0jznxwxi3x7fsjr836-spaces-integration-proton-tls.drv5error: Cannot build '/nix/store/yvmgn4qlsglqlc0jznxwxi3x7fsjr836-spaces-integration-proton-tls.drv'.6 Reason: builder failed with exit code 1.7 Output paths:8 /nix/store/lydpdgavm0gl2gb9ql502mka2m9aijvi-spaces-integration-proton-tls9 Last 17 log lines:10 > PASS: serving cert carries Basic Constraints CA:TRUE (mimics Proton Bridge)11 > === generate himalaya.toml + msmtprc via integration_proton._build_config ===12 > GENERATED himalaya.toml + msmtprc13 > === generated config: integration pins backend.encryption.cert + tls_trust_file ===14 > PASS: generated himalaya config pins backend.encryption.cert at the Bridge cert15 > PASS: generated msmtprc carries tls_trust_file at the Bridge cert16 > === IMAP positive: himalaya trusts the CA:TRUE cert via the integration's pin ===17 > FAIL: himalaya did NOT complete TLS (stub: IMAP_LISTEN 14143)18 > PASS: no CaUsedAsEndEntity / cert error from himalaya when pinned19 > === IMAP negative: strip the integration's pin -> default verifier rejects CA:TRUE ===20 > FAIL: expected a TLS rejection without pin, got: Suggestions: - Run with --log-level to enable more verbose logs21 > === SMTP positive: msmtp trusts the CA:TRUE cert via the integration's tls_trust_file ===22 > PASS: msmtp trusted the CA:TRUE cert via tls_trust_file (no cert error)23 > === SMTP negative: point trust_file at an unrelated cert -> msmtp must reject ===24 > PASS: msmtp rejected the mismatched cert (trust_file is enforced)25 >26 > RESULT: FAILURES27 For full logs, run:28 nix log /nix/store/yvmgn4qlsglqlc0jznxwxi3x7fsjr836-spaces-integration-proton-tls.drv