Koji is always very nice and it tells me whether a build failure was caused by
root.log or build.log. See for example:
BuildError: error building package (arch x86_64), mock exited with status 1; see
build.log for more information
Is Copr presenting this kind of information somewhere? (I need to fetch it for
hundreds of builds.)
I could probably HTTP HEAD the build.log and check Content-Length to guess a
root.log failure, but it feels weird...
Thanks for tips.
for some reason (not yet known, tracked in fedora infra ) ppc64le
builders fail to spawn, and what is even worse this issue also affects x86
builders. So because of this, we temporarily disabled ppc64le
architecture in copr. It means that the ppc64le builds will be processed
later once we enable it again; if you can't afford waiting (hours or
maybe days) please temporarily disable ppc64le chroots in your copr
Sorry for inconvenience,
I get failures in SRPM builds:
FileNotFoundError: [Errno 2] No usable temporary directory found in ['/tmp',
'/var/tmp', '/usr/tmp', '/home/mockbuilder']
It seem that individuals can requests permissions in individual coprs, but not
in group coprs. Is that correct?
I for example don't see the settings tab at @copr/copr (group) but I see it at