It also might be helpful to know that you can do:
fedpkg scratch-build [--srpm] --arches ppc64le
or, with qemu-user-static installed:
fedpkg mockbuild --root fedora-rawhide-ppc64le
which is quite slow but does allow you to play around in the chroot
after the build fails.
On 2/1/22 08:39, Dan Horák wrote:
> On Tue, 1 Feb 2022 06:34:10 -0700
> Brad Bell <bradbell(a)seanet.com> wrote:
>
>> I am having trouble with a build on the ppc64le arch.
>> I do not have such a machine for testing so that only way I can see to debug it
is to try patches in
>> the spec file that print diagnostic output.
>>
>> There is no point in running these tests on all the arch values, only the one
that is failing.
>> How do I do this ?
> all Fedora packagers have access to machines listed in
>
https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintai...,
> including a ppc64le one
>
> If this is a result from the mass rebuild, please make sure the bug is
> set to "Blocks" the PPCTracker bug.
>
>
> Thanks,
>
> Dan
> _______________________________________________
> packaging mailing list -- packaging(a)lists.fedoraproject.org
> To unsubscribe send an email to packaging-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproje...
> Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure