Description of problem: This is an excerpt from https://copr-be.cloud.fedoraproject.org/results/fif/wolpd/fedora-rawhide-i386/01094193-wolpd/build.log.gz + /usr/bin/gzip -dc /builddir/build/SOURCES/wolpd-1.0.6.tar.gz + /usr/bin/tar -xof - /usr/bin/tar: wolpd-1.0.6/config.aux/compile: Cannot utime: Operation not permitted /usr/bin/tar: wolpd-1.0.6/config.aux/depcomp: Cannot utime: Operation not permitted 8< snip >8 /usr/bin/tar: wolpd-1.0.6: Cannot utime: Operation not permitted /usr/bin/tar: Exiting with failure status due to previous errors RPM build errors: error: Bad exit status from /var/tmp/rpm-tmp.fM2yUt (%prep) Bad exit status from /var/tmp/rpm-tmp.fM2yUt (%prep) Child return code was: 1 EXCEPTION: [Error()] Traceback (most recent call last): How reproducible: Always Steps to Reproduce: 1.Submit a fedora-rawhide-i386 build to copr. Actual results: Build fails at untar in %prep stage. Expected results: Build should succeed.
This is systemd issue 1770154, we need to have it fixed on F30 to make the build work again with systemd nspawn. I already reported this against glibc before but I was redirected to systemd: https://bugzilla.redhat.com/show_bug.cgi?id=1771319 Perhaps we could turn off the systemd-nspawn in fedora-rawhide-i386 till we have the fix.
Work-around applied [1], it will take some time till the new config gets distributed to all builders. We'll close this bug once systemd allows us to drop the hack. [1] https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=4e2fbfaef78e5e3da40a603a415b53f56bdc1f07
Weird, build against fedora-rawhide-i386 passed for me now, even without the workaround applied: https://copr-be.cloud.fedoraproject.org/results/praiskup/ping/fedora-rawhide-i386/01112235-dummy-pkg/builder-live.log.gz
Should be fixed.