Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 915627 - app-containers/k3d: incompatible with dev-lang/go-1.21
Summary: app-containers/k3d: incompatible with dev-lang/go-1.21
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Zac Medico
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: go-1.21-bugs
  Show dependency tree
 
Reported: 2023-10-12 09:00 UTC by Richard
Modified: 2023-12-12 20:35 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
Output of emerge --info (emerge-info.txt,7.40 KB, text/plain)
2023-10-12 09:00 UTC, Richard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Richard 2023-10-12 09:00:47 UTC
Created attachment 872602 [details]
Output of emerge --info

I recently upgraded go to 1.21.1 and recompiled all go packages (@golang-rebuild) as recommended by emerge. Now, k3d is broken. It is not (yet) compatible with go 1.21.1 and the dependency should be restricted to something like <1.21.

There is a relevant but somewhat outdated issue: https://github.com/k3d-io/k3d/issues/1118

The error message that k3d prints:

$ k3d
panic: Something in this program imports go4.org/unsafe/assume-no-moving-gc to declare that it assumes a non-moving garbage collector, but your version of go4.org/unsafe/assume-no-moving-gc hasn't been updated to assert that it's safe against the go1.21 runtime. If you want to risk it, run with environment variable ASSUME_NO_MOVING_GC_UNSAFE_RISK_IT_WITH="go1.21" set. Notably, if go1.21 adds a moving garbage collector, this program is unsafe to use.

goroutine 1 [running]:
go4.org/unsafe/assume-no-moving-gc.init.0()
        /var/tmp/portage/app-containers/k3d-5.4.9/work/k3d-5.4.9/vendor/go4.org/unsafe/assume-no-moving-gc/untested.go:25 +0x1da
Comment 1 Richard 2023-12-12 20:35:28 UTC
I just tested building k3d-5.6.0 using go-1.21.4 and it works and runs fine.

This bug seems to be resolved by the recent bump to 5.6.0 and can be closed.