Created attachment 233571 [details] sysutils--govmomi update to 0.28.0 patch with update to govmomi 0.28.0 is in attachments.
govmomi is failed to build on go 1.18. my Golang expertise doesn't allow to fix it. anybody can help?
What's the error?
It was successful on go 1.17. But, with Go 1.18 upgrade make is failing with error: ===> Extracting for govmomi-0.28.0 => SHA256 Checksum OK for go/sysutils_govmomi/govmomi-v0.28.0/v0.28.0.mod. => SHA256 Checksum OK for go/sysutils_govmomi/govmomi-v0.28.0/v0.28.0.zip. github.com/vmware/govmomi/examples/alarms imports github.com/dougm/pretty: no required module provides package github.com/dougm/pretty; to add it: go get github.com/dougm/pretty github.com/vmware/govmomi/govc/object imports github.com/a8m/tree: no required module provides package github.com/a8m/tree; to add it: go get github.com/a8m/tree github.com/vmware/govmomi/toolbox imports github.com/rasky/go-xdr/xdr2: no required module provides package github.com/rasky/go-xdr/xdr2; to add it: go get github.com/rasky/go-xdr/xdr2 *** Error code 1 ======== %< ========= These modules updates a long time ago. Actually, I see several reported bugs with the same error about other Go-built ports after Go upgrade.
Builds fine for me with 1.18. Could be worth doing `make distclean` before the build.
The build is successful after 'make distclean'. Sorry for the false alarm, have got mentioned error for another Go 1.18 and thought this is affected too. Thank you!
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=e770798d89f120b285c2cb398ecb2230e1a85f8f commit e770798d89f120b285c2cb398ecb2230e1a85f8f Author: Aleksandr Ignatyev <alex@i.org.ua> AuthorDate: 2022-04-30 15:13:16 +0000 Commit: Dmitri Goutnik <dmgk@FreeBSD.org> CommitDate: 2022-04-30 15:13:16 +0000 sysutils/govmomi: Update to 0.28.0 Changes: https://github.com/vmware/govmomi/releases/tag/v0.28.0 PR: 263644 sysutils/govmomi/Makefile | 3 +-- sysutils/govmomi/distinfo | 10 +++++----- 2 files changed, 6 insertions(+), 7 deletions(-)
Np, thanks for the update. Looks like the Go module cache became stale, which shouldn't happen.