You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As soo as I want to keep all my packages up-to-date and use go get -u all it also updates x/sys@upgrade to 0.13.0 and then reports that golang.org/x/sys/internal/unsafeheader is missing.
What did you expect to see?
No error? :)
What did you see instead?
This error:
all: module golang.org/x/sys@upgrade found (v0.13.0), but does not contain package golang.org/x/sys/internal/unsafeheader
The text was updated successfully, but these errors were encountered:
@seankhliao Yes, indeed, it is no longer there. But why "go get -u all" return an error if no code use it? I think that is why the OP post it and me comment it here.
$ cat go.mod
module github.com/shuLhan/share
go 1.20
require (
golang.org/x/crypto v0.13.0
golang.org/x/net v0.15.0
golang.org/x/sys v0.12.0
golang.org/x/term v0.12.0
)
//replace golang.org/x/term => ../../../golang.org/x/term
$ git status
On branch dev
Your branch is up to date with 'origin/dev'.
Untracked files:
(use "git add <file>..." to include in what will be committed)
testdata/
nothing added to commit but untracked files present (use "git add" to track)
$ go get -u all; echo $?
go: all: module golang.org/x/sys@upgrade found (v0.13.0), but does not contain package golang.org/x/sys/internal/unsafeheader
1
$ git --no-pager diff
$
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes, only the lastest (
0.13.0
)Works fine with
0.12.0
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
As soo as I want to keep all my packages up-to-date and use
go get -u all
it also updatesx/sys@upgrade
to0.13.0
and then reports thatgolang.org/x/sys/internal/unsafeheader
is missing.What did you expect to see?
No error? :)
What did you see instead?
This error:
The text was updated successfully, but these errors were encountered: