This is a similar issue to https://pagure.io/golist/issue/3 this time for packagers that try to package several import paths in a single spec (I’m told the practice is common RHEL-side).

For this use pattern to work reliably, you need to compute the codebase requirements in a single pass. Otherwise golist will forget to filter out imports of code, already available on-system under another import path. And that will break the BuildRequires computation being worked on for
https://github.com/rpm-software-management/rpm/pull/593 or
https://pagure.io/fesco/issue/2004 are done.

So we need something like

$ golist --imported --skip-self --with-tests --package-path %{goipath0} --package-path %{goipath1} --package-path %{goipath2}