On Sunday, June 12, 2022 1:52:54 PM CDT Denis Fateyev wrote:
Hello,
I'm playing with "golang-x-sys" package in Fedora [1], testing it and rebuilding locally and in Koji (scratch builds).
I've got confused with one thing: looking at the latest F36 update [2] — the package build / update was successful. But, grabbing the SRPM from there and scratch-building it with Koji under F36 and EPEL9, I got errors: [3], [4].
- For EPEL9: build failed due "noarch" package differences under several
platforms;
- For F36: build failed due to issues with "s390x" architecture.
Did I miss anything to build this package in these branches properly?
I've requested to push "golang-x-sys" to EPEL9 [5], so interested in any possible build peculiarities there. If you have any information, please let me know. Thanks!
[1] https://src.fedoraproject.org/rpms/golang-x-sys
[2] https://koji.fedoraproject.org/koji/buildinfo?buildID=1976849
[3] https://koji.fedoraproject.org/koji/taskinfo?taskID=88189716
[4] https://koji.fedoraproject.org/koji/taskinfo?taskID=88189719
Hi Denis,
Fyi, I'm not the primary of this package (@eclipseo is), but I occasionally help out with its maintenance as a member of the go-sig. That being said, I'm happy to help to the best of my ability :).
I was not able to reproduce the F36 s390x failure, either yesterday or when I initially built the package. That may have been a transient infra issue.
I'm a bit stumped regarding the EPEL 9 issue. go-rpm-macros is actually part of RHEL 9 and is not maintained by us. The RHEL maintainers made some minor changes to the go-rpm-macros package from Fedora. I wonder if those could be the culprit.
[/me thinks some more and has an idea...]
I tested two builds of golang-x-sys on epel9-next: one with the version of go-rpm-macros present in c9s and another one built against Rawhide's go-rpm-macros and golist (the rest of the packages were the standard CentOS Stream/EPEL 9 packages). I was able to use go-rpm-macros and golist that were built on Koji for Rawhide on c9s, because go-rpm-macros doesn't have any compiled code and golist is statically linked. This points to some issue with EL 9's go-rpm-macros package.
In the first build, the -devel package had different contents on different architectures, while it didn't in the second build. I've CC'd the golang mailing list and the go-rpm-macros maintainer to see if they have any input.
golang@lists.fedoraproject.org