Do the COPR environments either support faccessat2 or fail with ENOSYS?
I've been told that we put in a workaround in glibc for the bogus EPERM
error from systemd-nspawn specifically to support COPR:
And we really need to remove that workaround again because EPERM is an
ambiguous error code and applies to situations where we *do not* want to
perform the fallback implementation (because it cannot perform
permission checks accurately).
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill