qulogic reported a new issue against the project: `go-rpm-macros` that you are following:
``
In the old version of [golang-github-pkg-errors](https://src.fedoraproject.org/rpms/golang-github-…, there was a typo, and `glide.yaml` was listed twice in the sources. This meant that `glide.lock` was never copied to the source directory.
When `%goinstall glide.yaml glide.lock` was called later, it created a `glide.lock` _directory_. Now that I'm trying to fix it, it causes [an upgrade error](https://bodhi.fedoraproject.org/updates/FEDORA-2019-f01a015bb7#comme… since rpm can't handle a directory->file change. So now I need to go throw in a scriptlet to fix the directory.
`%goinstall` should not accept an explicit path argument that does not exist, and should fail the build. If it really needs to be able to create arbitrary directories like that, it should be behind an explicit flag (like `install -d` is).
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/issue/7
nim reported a new issue against the project: `go-rpm-macros` that you are following:
``
This is a clone of
https://github.com/gofed/go-macros/issues/56
The problem is actually in golist, not in the macros themselves. Sticking it in the macro project for now as they need to be switched to deploy in libdir if this is not fixed
According to @jcajka this needs fixing in any case, because other build options are handled the same way by the Go compiler, so deploying only the files corresponding to a particular set of options means sources can not be used with another one later. And we have some of those in Fedora, for example, optional selinux support in some container projects.
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/issue/1
nim reported a new issue against the project: `go-rpm-macros` that you are following:
``
The macro code needs massaging to also work on EPEL.
Most of the work is spec side since some of the macros are going to collide with the ones provided by previous iterations of Go macro packages
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/issue/2
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
nim opened a new pull-request against the project: `go-rpm-macros` that you are following:
``
make it use the actual code that was merged in redhat-rpm-config-130
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/16
nim opened a new pull-request against the project: `go-rpm-macros` that you are following:
``
small fixes
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/15