Just a heads-up for anyone experiencing build failures like me.
Recently the forge macros were ported to use distprefix on f30. An
unrelated change followed and a new build was pushed to rawhide (maybe
without realising that it would also push the forge macro changes).
This change was introduced with redhat-rpm-config-121-1.fc30.
It looks like the forge macros weren't tested to be backwards
compatible, because packages that build successfully now fail to build
on rawhide (see, for example, build [0]).
The reason: The %{gosource} macro now expands to a different string on
rawhide. So, sources uploaded on <f30 won't be found by koji's
buildSRPMfromSCM on rawhide, and vice versa - see the failed SRPM
build [1].
The difference is the inclusion (or lack thereof) of a leading "v"
from the tag in the file name. Up to f29, it will include the leading
"v" in the Source tag (and file download, and source file entry, and
lookaside cache file), and on rawhide, it won't.
!!! This will break koji builds of all packages that use the forge macros
!!! (with a tag, not a commit) in rawhide.
!!! Koschei builds are already starting to fail because of this change.
Since backporting the change won't work due to distprefix not being
available, I think the leading "v" in the version part of the Source
tag has to be reintroduced.
But I won't upload two differently named source archives to the
lookaside cache just for building the same version of a package on
different releases of fedora.
I reported this issue at [2].
Fabio
[0]:
https://koji.fedoraproject.org/koji/taskinfo?taskID=30225034
[1]:
https://kojipkgs.fedoraproject.org//work/tasks/5035/30225035/build.log
[2]:
https://bugzilla.redhat.com/show_bug.cgi?id=1639025