Comment 6 for bug 1637554

Revision history for this message
Barry Warsaw (barry) wrote :

Actually, hmm. The cp error message is different in the afp case, so maybe hgfs has different semantics than afp after all.

Note that even with the operation not supported error, the resulting file is checksum equivalent, which means that `cp --preserve` is failing after the bits are copied. How much does it matter that the mode, ownership, and timestamp are preserved? I've already laid out why I think the timestamp doesn't matter as much. In my own tests over afp, the ownership of the new file is equivalent to the remote user's uid anyway. It's true that the remote file (after the exception) does not honor umask of either the source umask or target umask.

So another option would be: catch the CalledProcessError and if the checksums of the copied file are not equivalent to the source file, re-raise the exception. If they're equivalent, swallow the error.

Or we could just remove -p and be done with it.