Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here contains two patches:
One from modification of
PKGBUILDcalledriscv46.The other from upstream, which fixed the original error:
assume-no-moving-gc.Because upstream fixed this error without new release found, so I just change their modification into a patch then apply it in our packages.
Notice: in their modification,
goneed download new version, however,build()ofPKGBUILDhas a optionexport GOPROXY=off, which can lead this into failure, so I delete it.If there is any wrong management, please fell free to tell me, thanks.
Build passed.
Related issue and pull request:
Issue: grafana/agent#1983
PR: grafana/agent#1985
Original error message:
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.19 runtime. If you want to risk it, run with environment variable ASSUME_NO_MOVING_GC_UNSAFE_RISK_IT_WITH=go1.19 set. Notably, if go1.19 adds a moving garbage collector, this program is unsafe to use.