On Fri, Jul 29, 2022 at 12:53 PM Florian Weimer <fweimer(a)redhat.com> wrote:
Pretty much all Go compiler error messages contain the chracter sequence
“.go:”. Using that, we end up at:
Good to know. I'll add it to my mental list of things to "grep" for.
cannot use "The version of quic-go you're using can't be built on Go 1.19
yet. For more details, please see
string constant "The version of quic-go you're using can't be built on Go
1.19 yet. F...) as int value in variable declaration
Which is pretty self-explanatory.
Thanks, I wouldn't have found that in the wall of text. But true, this
is pretty self-explanatory.
In fact, I've had this problem with quic-go before with major Go
version bumps ...
The quic-go library has specific "forks" that support only one major
Go version each. Syncthing imports them all, and then uses conditional
compilation at build-time, depending on the actual version of the
compiler. So I won't be able to fix this until 1) quic-go releases a
version of their library that's specific to go 1.19, and 2) syncthing
adds support for go 1.19.
I can't fix the resulting FTBFS issue myself, but at least now I know
what's going on.
Still, not getting included in rebuilds for golang CVE fixes now is
kind of a bummer.