From 2ed947897bc6ceb2a59ff0f3d90a5ee185c8daa3 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog" Date: Wed, 16 Apr 2014 21:20:43 +0000 Subject: [PATCH] --- ...c_transfer_is_interrupted_and_resumed.mdwn | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed.mdwn diff --git a/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed.mdwn b/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed.mdwn new file mode 100644 index 0000000000..30dfb6eb72 --- /dev/null +++ b/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed.mdwn @@ -0,0 +1,28 @@ +### Please describe the problem. + +umask is 022 on both hosts +If one does ls -lL on source repo, the files are shown 644. + +Now, "git annex get" from a clone done over ssh generally preserves 644 ... except if the transfer (rsync) is interrupted, and then resumed. +In fact, looks like the temp files in .git/annex/tmp have the og+r bits cleared during the resumed transfer. + +So this is inconsistent: I don't see why permissions should be different, depending whether or not there was an interruption in the transfer. +Plus, og+r permissions can actually be important for setups like serving contents using Samba. + +### What steps will reproduce the problem? + + +### What version of git-annex are you using? On what operating system? + +git-annex version: 5.20140411-gda795e0 +Linux + +### Please provide any additional information below. + +[[!format sh """ +# If you can, paste a complete transcript of the problem occurring here. +# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log + + +# End of transcript or log. +"""]]