Bug 277203 - devel/go-wire: update to 0.6.0
Summary: devel/go-wire: update to 0.6.0
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL: https://github.com/google/wire/releas...
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-20 20:11 UTC by Denis Shaposhnikov
Modified: 2024-04-20 23:59 UTC (History)
2 users (show)

See Also:
drtr0jan: maintainer-feedback+


Attachments
update devel/go-wire to 0.6.0 (1.75 KB, patch)
2024-02-20 20:11 UTC, Denis Shaposhnikov
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Denis Shaposhnikov 2024-02-20 20:11:30 UTC
Created attachment 248649 [details]
update devel/go-wire to 0.6.0

This patch updates devel/go-wire to 0.6.0:

https://github.com/google/wire/releases/tag/v0.6

Fix build with added patch, which actually adds `# explicit; go 1.18`:

```
 # golang.org/x/tools v0.17.0
+## explicit; go 1.18
```

without it we are getting errors:

```
vendor/golang.org/x/tools/internal/event/keys/util.go:14:11: type parameter requires go1.18 or later (-lang was set to
.16; check go.mod)
vendor/golang.org/x/tools/internal/event/keys/util.go:14:13: embedding interface element ~[]T requires go1.18 or later
ang was set to go1.16; check go.mod)
vendor/golang.org/x/tools/internal/event/keys/util.go:14:21: embedding interface element ~string requires go1.18 or la
(-lang was set to go1.16; check go.mod)
vendor/golang.org/x/tools/internal/event/keys/util.go:15:32: invalid argument: s (variable of type S constrained by ~[]T) for len
vendor/golang.org/x/tools/internal/event/keys/util.go:16:20: cannot range over s (variable of type S constrained by ~[]T): no core type
vendor/golang.org/x/tools/internal/versions/types.go:15:16: predeclared any requires go1.18 or later (-lang was set to go1.16; check go.mod)
```

See https://github.com/golang/go/issues/54908 for more details.
Comment 1 Boris Korzun 2024-02-20 21:10:53 UTC
Hi Denis,

what do you think, isn't needed to open the issue on a upstream (github.com/google/wire)?
Comment 2 Denis Shaposhnikov 2024-02-20 22:11:50 UTC
(In reply to Boris Korzun from comment #1)
It would be best option, but I just can't imagine what exactly we'll ask. Will we ask them bump go version just because we have troubles with building it using FreeBSD port system?

OK, I created the issue:

https://github.com/google/wire/issues/404

I see https://github.com/google/wire is stagnating, so I'm not expecting this issue will be resolved upstream. I'd suggest apply my patch, until upstream resolve it.
Comment 3 Boris Korzun 2024-02-21 07:39:06 UTC
Comment on attachment 248649 [details]
update devel/go-wire to 0.6.0

Tested, approved. LGTM.
Comment 4 Peter Jeremy freebsd_committer freebsd_triage 2024-04-20 23:59:15 UTC
I would also support this patch being applied - both because the patch works and because I am seeing consistent nil pointer exceptions with v0.5.0