Issues with go1.23 when building kuttl, kubeconform, teleport and possibly others
Hi all, today I noticed that my SR for kuttl (that is open for 21 days) shows the package as failing for Tumbleweed, while it was fine when I created the SR. After doing some digging I noticed that I can build (locally) when using go1.22 ("BuildRequires: go1.22") and not go1.23rc1. Same seems to hold true for kubeconform and possibly teleport. All of them are failing to build on OBS, but if I change the BuildRequires for go to the following, the build passes: BuildRequires: go1.22 My (naive) assumption is that something in go1.23 RC1 is not fully working, or the packages need adaptions to work with it? Kind Regards Johannes
Thanks for the report. go1.23rc1is in Factory and final release is estimated to be two weeks out. I'll take a look at the failing build. Jeff Kowalczyk On Thu, Aug 1, 2024 at 6:43 AM Johannes Kastl <mail@johannes-kastl.de> wrote:
Hi all,
today I noticed that my SR for kuttl (that is open for 21 days) shows the package as failing for Tumbleweed, while it was fine when I created the SR.
After doing some digging I noticed that I can build (locally) when using go1.22 ("BuildRequires: go1.22") and not go1.23rc1.
Same seems to hold true for kubeconform and possibly teleport.
All of them are failing to build on OBS, but if I change the BuildRequires for go to the following, the build passes:
BuildRequires: go1.22
My (naive) assumption is that something in go1.23 RC1 is not fully working, or the packages need adaptions to work with it?
Kind Regards Johannes
-- -- Jeff Kowalczyk Software Engineer, Go Developer Experience SUSE Linux Email jkowalczyk@suse.com Timezone US/Pacific http://suse.com
Hi Jeff, On 02.08.24 05:41 Jeff Kowalczyk via openSUSE Factory wrote:
Thanks for the report. go1.23rc1is in Factory and final release is estimated to be two weeks out. I'll take a look at the failing build.
Thanks!
On Thu, Aug 1, 2024 at 6:43 AM Johannes Kastl <mail@johannes-kastl.de> wrote:
Same seems to hold true for kubeconform and possibly teleport.
I committed the fix for teleport (BuildRequire go1.22 exactly) to have OBS build it, as it is a rather large package and building locally is no fun. But the two other packages are still in failing state on OBS. Kind Regards, Johannes
Hello Johannes, Am Freitag, 2. August 2024, 08:17:58 MESZ schrieb Johannes Kastl:
Same seems to hold true for kubeconform and possibly teleport.
I committed the fix for teleport (BuildRequire go1.22 exactly) to have OBS build it, as it is a rather large package and building locally is no fun. But the two other packages are still in failing state on OBS.
version pinning is not a solution in the long run, as TW will move on. Sooner or later the packages must be adapted - or they get removed from TW (like the hylafax package after the libtiff 4.6.0 upgrade, which removed needed functionality - but thats a different story) Cheers Axel
Hi Axel, On 02.08.24 08:25 Axel Braun wrote:
Am Freitag, 2. August 2024, 08:17:58 MESZ schrieb Johannes Kastl:
Same seems to hold true for kubeconform and possibly teleport.
I committed the fix for teleport (BuildRequire go1.22 exactly) to have OBS build it, as it is a rather large package and building locally is no fun. But the two other packages are still in failing state on OBS.
version pinning is not a solution in the long run, as TW will move on. Sooner or later the packages must be adapted - or they get removed from TW (like the hylafax package after the libtiff 4.6.0 upgrade, which removed needed functionality - but thats a different story)
Sorry, you misunderstood me, but I was unclear in the above. Instead of trying out the fix locally (which takes ages due to the large package) I commited the fix in my branch only, to see if this also fixes the issue for teleport. And yes, it does. I do not plan to submit the pinned version to Tumbleweed, unless this turns out to be a bigger issue with the go1.23 package. Kind Regards, Johannes
participants (3)
-
Axel Braun -
Jeff Kowalczyk -
Johannes Kastl