nim reported a new issue against the project: `go-rpm-macros` that you are following: `` To workaround https://pagure.io/golist/issue/7, the shell wrapper should switch to another directory (for example /usr/bin) before running `golist`, and switch back to the correct dir afterwards (so add strategic pushds popds to keep track of where the user, golist and the tests want to be) ``
To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/issue/6
The issue: `golist needs to be run outside the source tree to avoid panics` of project: `go-rpm-macros` has been assigned to `nim` by nim.
qulogic added a new comment to an issue you are following: `` Based on [further debugging](https://pagure.io/golist/issue/7#comment-551104), this appears related to Go modules. As such, an alternate workaround is to set `GO111MODULES=off` before calling `golist`. Of course, you need to be sure your package doesn't actually _use_ Go modules to specify an alternate path or whatever. ``
To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/issue/6
The status of the issue: `golist needs to be run outside the source tree to avoid panics` of project: `go-rpm-macros` has been updated to: Closed by nim.
nim added a new comment to an issue you are following: `` Modules are now disabled by default, module mode will require a new tooling stack refresh anyway. Closing ``
To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/issue/6
golang@lists.fedoraproject.org