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
I did an update in a project that uses this module; my handy update script just requests each directly required module @latest. The recent addition of a package at the top level without any buildable files (since the one file is guarded by a build tag) makes go get unhappy:
$ go get -d mvdan.cc/sh/v3@latest
mvdan.cc/sh/v3: no Go source files
Does the root directory need an unguarded file to ensure that the package is buildable, or maybe have its code moved to some other directory?
The text was updated successfully, but these errors were encountered:
You're right, and I can reproduce on 1.16.4. This seems to be golang/go#33526, which in theory did get fixed in 1.16.x, but I still see the error. I left a comment there.
It seems like this bug is fixed on Go master as of go version devel go1.17-ce92a2023c Sat May 15 02:39:08 2021 +0000 linux/amd64, as I can no longer reproduce. But I'll add a workaround since 1.15.x and 1.16.x might suffer from this bug for a while still.
I did an update in a project that uses this module; my handy update script just requests each directly required module
@latest
. The recent addition of a package at the top level without any buildable files (since the one file is guarded by a build tag) makesgo get
unhappy:$ go get -d mvdan.cc/sh/v3@latest mvdan.cc/sh/v3: no Go source files
Does the root directory need an unguarded file to ensure that the package is buildable, or maybe have its code moved to some other directory?
The text was updated successfully, but these errors were encountered: