On Mon, 2025-01-20 at 21:00 +0100, Simon Josefsson wrote: > Although shouldn't the FTBFS bug really on 'sigstore-go' rather than > 'golang-github-google-certificate-transparency'? The former is what is > failing to build, not the latter. It would have been nice if the > g-g-g-c-t test suite triggered these APIs too. I can see it make sense > to keep 'golang-github-google-certificate-transparency' out of testing > until we sort this out though.
The cause of the failure, though, isn't in sigstore-go, but in the newer version of g-g-g-c-t. That's why I reported the bug against that package. I did tag with ftbfs; maybe that wasn't quite correct. On Wed, 2025-01-22 at 21:57 +0000, Simon Josefsson wrote: > Bug #1093640 in sigstore-go reported by you has been fixed in the > Git repository and is awaiting an upload. You can see the commit > message below and you can check the diff of the fix at: > > https://salsa.debian.org/go-team/packages/sigstore-go/-/commit/2ec12dceb0d5b9f088c1ea697a5b2f38934ebb55 This looks like it's just papering over the issue. Any other package down the road that tries to use certificate-transparency- go/trillian/ctfe/storage/postgresql will also fail. g-g-g-c-t should either not ship that bit of code, or add the necessary package among its Build-Depends and Depends. (I think it was just golang-github- jackc-pgerrcode-dev when I was looking at this last week.) Mathias
signature.asc
Description: This is a digitally signed message part
