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
Running "go get -v golang.zx2c4.com/wireguard/wgctrl" gives the following output:
get "golang.zx2c4.com/wireguard/wgctrl": found meta tag get.metaImport{Prefix:"golang.zx2c4.com/wireguard/wgctrl", VCS:"git", RepoRoot:"https://github.com/WireGuard/wgctrl-go"} at //golang.zx2c4.com/wireguard/wgctrl?go-get=1
golang.zx2c4.com/wireguard/wgctrl (download)
get "golang.org/x/crypto/curve25519": found meta tag get.metaImport{Prefix:"golang.org/x/crypto", VCS:"git", RepoRoot:"https://go.googlesource.com/crypto"} at //golang.org/x/crypto/curve25519?go-get=1
get "golang.org/x/crypto/curve25519": verifying non-authoritative meta tag
golang.org/x/crypto (download)
get "golang.org/x/sys/windows": found meta tag get.metaImport{Prefix:"golang.org/x/sys", VCS:"git", RepoRoot:"https://go.googlesource.com/sys"} at //golang.org/x/sys/windows?go-get=1
get "golang.org/x/sys/windows": verifying non-authoritative meta tag
golang.org/x/sys (download)
get "golang.zx2c4.com/wireguard/ipc/winpipe": found meta tag get.metaImport{Prefix:"golang.zx2c4.com/wireguard", VCS:"git", RepoRoot:"https://git.zx2c4.com/wireguard-go"} at //golang.zx2c4.com/wireguard/ipc/winpipe?go-get=1
get "golang.zx2c4.com/wireguard/ipc/winpipe": verifying non-authoritative meta tag
golang.zx2c4.com/wireguard (download)
package golang.zx2c4.com/wireguard/ipc/winpipe: C:\Users\nicka\go\src\golang.zx2c4.com\wireguard exists but C:\Users\nicka\go\src\golang.zx2c4.com\wireguard.git does not - stale checkout?
Running from a linux machine (or WSL), the go get completes ok, so this issue seems to be windows specific
The text was updated successfully, but these errors were encountered:
Running "go get -v golang.zx2c4.com/wireguard/wgctrl" gives the following output:
Running from a linux machine (or WSL), the go get completes ok, so this issue seems to be windows specific
The text was updated successfully, but these errors were encountered: