https://bugzilla.redhat.com/show_bug.cgi?id=2019329
--- Comment #3 from Pavel Raiskup <praiskup(a)redhat.com> ---
Disabling nosync in mock fixes the issue.
Yes. Well: s/fixes the issue/makes the build succeed/ because we don't want
to disable nosync in mock :-)
It seems that nosync.so+mock always worked this way (nosync from host used
inside the target-chroot).
It's weird that this problem is happening for the first time right now.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2019329