Learn more about these different git repos.
Other Git URLs
See e.g. https://koji.fedoraproject.org/koji/buildinfo?buildID=815300
From the build logs of the different architectures --docdir=%{_pkgdocdir} expands to
on aarch64: --docdir=/usr/share/doc/globus-common-16.8
on x86_64, ppc64 and ppc64le: --docdir=/usr/share/doc/globus-common
And even though the build on all architectures succeed, the task fails because the noarch packages created on different architectures do not agree.
I think it is aarch64 that is correct, and the other three that have started to get it wrong, at least that is how it used to be. All four architectures still agrees that %_licensedir is defined with the version.
See also:
https://bugzilla.redhat.com/show_bug.cgi?id=1392354
This bug is about the broken redhat-rpm-config, which is part of the problem.
But why does different architectures in EPEL 7 koji use different versions of rpm and redhat-rpm-config?
aarch64: redhat-rpm-config.noarch 0:9.1.0-68.el7 rpm.aarch64 0:4.11.3-17.el7
x86_64: redhat-rpm-config.noarch 0:9.1.0-72.el7 rpm.x86_64 0:4.11.3-21.el7
ppc64: redhat-rpm-config.noarch 0:9.1.0-72.el7 rpm.ppc64 0:4.11.3-21.el7
ppc64le: redhat-rpm-config.noarch 0:9.1.0-72.el7 rpm.ppc64le 0:4.11.3-21.el7
These packages come from Red Hat, you would have to ask them.
See also: https://bugzilla.redhat.com/show_bug.cgi?id=1392354 This bug is about the broken redhat-rpm-config, which is part of the problem. But why does different architectures in EPEL 7 koji use different versions of rpm and redhat-rpm-config?
We had an issue pulling down 7.3 for aarch64, I thought that was fixed. I'll escalate.
aarch64: redhat-rpm-config.noarch 0:9.1.0-68.el7 rpm.aarch64 0:4.11.3-17.el7 x86_64: redhat-rpm-config.noarch 0:9.1.0-72.el7 rpm.x86_64 0:4.11.3-21.el7 ppc64: redhat-rpm-config.noarch 0:9.1.0-72.el7 rpm.ppc64 0:4.11.3-21.el7 ppc64le: redhat-rpm-config.noarch 0:9.1.0-72.el7 rpm.ppc64le 0:4.11.3-21.el7
https://koji.fedoraproject.org/koji/taskinfo?taskID=16339609 I have made sure we have 7.3 for aarch64 and your build is now working
@ausil changed the status to Closed
Closed
Login to comment on this ticket.