Santiago Vila <[email protected]> writes: > On Sat, Feb 07, 2026 at 01:15:32PM +0100, Stephen Kitt wrote: >> Hi Simon, >> >> On Sat, 07 Feb 2026 08:47:45 +0100, Simon Josefsson <[email protected]> >> wrote: >> > 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. >> >> How about >> >> Build-Depends: golang-go (>= 2:1.25~) > > That's future-proof, but afaik not "present-proof" because the current > golang-go package in unstable is still at version 2:1.24~2.
Indeed - I don't know when golang-go from golang-defaults will be updated to 1.25. So using this will just mean Nebula won't get built. Was that your intent Stephen? Maybe just opening a bug report for Nebula asking to drop the golang-1.25-go hack whenever golang-go is >= 1.25 is okay. I mostly worry about forgetting about this hack and then it will cause problems in a couple of months/years. > If you don't mind that the package is not built at all until > golang-go is updated in unstable, I think that's good enough. > It's like uploading to delayed queue, except that it's not the upload > what it's delayed but the build itself (until it can happen). I think it is best if Nebula is built using golang-go 1.25 which is in testing, to allow testing of it as early as possible. There is some positive feedback already, but more testing always helps. /Simon
signature.asc
Description: PGP signature
