(In reply to Dmitry V. Levin from comment #4) > Just letting you know that we reverted commit > 6b89c385d8bd0700b25bac2c2d0bebe68d5cc05d in our glibc build shortly after > reporting this issue.
Reading rsync bug report, I really think that EOPNOTSUPP is the correct error code to return in this case. The configure was done on a build system where lchmod does work (since it has procps mounted). So I do not fully agree this really characterizes as a regression. And I don't think reverting lchmod support since propcs might be not available is the correct approach, best option would try to ask kernel to have proper syscall support which does not require userland hacks. Rick Felker already sent a patch, but it seems to be stuck. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902109 Title: rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1902109/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
