On 2024-12-13 at 10:32:22, Konrad Bucheli (PSI) wrote: > My suggestion is not to silently ignore all chmod errors, only ENOTSUP for > config.lock which basically tells that it is not a suitable location for > that operation and thus also not required. > Would that be acceptable? That solves your particular problem, but the WSL situation gets EPERM[0], so it would not solve the general problem. We definitely don't want to blindly ignore EPERM in general for `config.lock` because it could indicate a real permissions problem or a race condition with other software. [0] https://askubuntu.com/questions/1115564/wsl-ubuntu-distro-how-to-solve-operation-not-permitted-on-cloning-repository -- brian m. carlson (they/them or he/him) Toronto, Ontario, CA
Attachment:
signature.asc
Description: PGP signature
