All, Nebula requires golang 1.25 or later (for some crypto stuff, compilation fails with 1.24 [1]), and I solved this by adding 'golang-1.25-go' as a Build-Depends and added
export PATH := /usr/lib/go-1.25/bin:$(PATH) to debian/rules. This works but it is ugly. It will do the wrong thing when 1.26+ becomes the default, keeping this package stuck on 1.25. Is there a more future proof pattern to use for this situation? I suppose this isn't a new situation, but I didn't run across how to solve it before. /Simon [1] https://salsa.debian.org/jas/nebula/-/jobs/8980373 says: src/github.com/slackhq/nebula/cert/cert_v1.go:117:24: undefined: ecdsa.ParseUncompressedPublicKey src/github.com/slackhq/nebula/cert/cert_v2.go:156:24: undefined: ecdsa.ParseUncompressedPublicKey src/github.com/slackhq/nebula/cert/sign.go:57:20: undefined: ecdsa.ParseRawPrivateKey
signature.asc
Description: PGP signature
