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:
<https://bugzilla.redhat.com/show_bug.cgi?id=1869030> 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). Thanks, Florian -- 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 _______________________________________________ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.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.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
