Mathias Gibbens

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050523; it appears that something in go 1.21 has broken this, but I haven't dug into it very much.

@maxkratz, what version of lxc-templates were you using? Vanilla lxc-templates creates a line similar to ``` deb http://security.debian.org/ bullseye-security main ``` and lxc-templates as packaged in bookworm produces a line...

Do you know how those test files were created? I do have access to the Debian porter boxes, so I can help debug/fix this in a s390x environment.

Debian packaging typically tries to stick to released versions, and version 1.2.1 expects fxamacker/cbor v2.4.0. Since that release, https://github.com/veraison/go-cose/pull/166 was merged into main, with changes for the fxamacker/cbor v2.5.0 release....

> BTW, go-cose@latest is v1.1.0 The latest tag of go-cose is v1.2.1 (https://github.com/veraison/go-cose/tags), which is what the Debian packaging tools are picking up on. > Interesting. OK, so to try...

It's resolved in Debian... by cherry-picking #166. I don't see any new tag/release that includes that PR. I don't directly use this library, so I'm not particularly invested in if...

Yeah, I haven't been able to reproduce this exact failure myself. Would adding `LIBDQLITE_TRACE=1` when running the tests have any adverse side effects? If not, I'll just add it to...

I've enabled `LIBDQLITE_TRACE=1` when running the tests, and it will be included whenever the next upload of dqlite is made to unstable.