nim reported a new issue against the project: `golist` that you are following:
``
This is the root cause behind
https://pagure.io/go-rpm-macros/issue/1
When asked to list the files to deploy, golist only answers for the current tags (arch and
build options)
https://pagure.io/go-rpm-macros/blob/master/f/bin/go-rpm-integration#_386
Being arch-specific is annoying but not a blocker¹
However @jcajka thinks this will also remove installation of files not covered by current
build tags. And that is a huge problem because that makes the result unusable, by any
consumer, that needs a different tag combination than the one passed by the source code
packager.
¹ The migration of Fedora’s go -devel packages to an arch-specific root can be kludged as
evidenced by
https://copr.fedorainfracloud.org/coprs/nim/go-rpm-macros/builds/ because
they are only installed transiently
``
To reply, visit the link below or just reply to this email
https://pagure.io/golist/issue/2