The ppc64le was disabled because premake 5.0-beta4 did not support ppc64. However 5.0-beta7 now does. Can we please backport https://gitea.wildfiregames.com/0ad/0ad/commit/638c04987ef134edea2b87d5f97996219206cebb and also ask the upstream people to bump theirs from 5.0-beta6 to 5.0-beta7? Many thanks Reproducible: Always
Upstream has bumped to beta7 ref: https://gitea.wildfiregames.com/0ad/0ad/commit/59cb3cd67b2b51a5bcc9d052d8d77e2f2a4b89b7
If you are to adopt the https://gitea.wildfiregames.com/0ad/0ad/commit/638c04987ef134edea2b87d5f97996219206cebb, please be aware that the changes to `build/premake/premake5.lua` file requires `semver` Lua package which is unavailable in Fedora. I think we could simply remove all codes from line 1 to 8 as a workaround.
Still fails: https://kojipkgs.fedoraproject.org/work/tasks/1004/137411004/build.log
> Still fails: https://kojipkgs.fedoraproject.org/work/tasks/1004/137411004/build.log @Gwyn: Have you backport those patches from upstream?
Yes.
@Gwyn could you please give me the git branch that contains the patch so I could try to locally build it? Many thanks
Sorry, there was a patch issue. Once I adapted the patches to 0.27.1, it fails because premake-core-5.0.0-beta4.tar.gz is present, not premake-core-5.0.0-beta7.tar.gz. I'm troublehsooting from that point on, I hope to make progress today.
FEDORA-2025-d67d57ec22 (0ad-0.27.1-5.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-d67d57ec22
FEDORA-2025-d67d57ec22 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-d67d57ec22` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-d67d57ec22 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-d67d57ec22 (0ad-0.27.1-5.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.