Hi Achim, On Tue, 09 Feb 2016 11:40:54 -0800, Achim Gratz <strom...@nexgo.de> wrote: > > Erik Hetzner writes: > > Sorry - I misunderstood how `org-test-for-executable' works. I’ll fix the > > issue. > > Thanks. > > > As for the rm -rf, it does not work in the way you suggest, at least on > > ubuntu > > GNU/Linux. Here is the result I get locally without the chmod: > > For pete's sake, what are the permissions? As I said, the only reason I > see that is happening is if the directory containing the files is mode > 55x. And that would either be spectactularly stupid or exceptionally > clever, although I tend toward the first interpretation. In any case, > you'd need to make the directories writable to fix this, but not the > files. There might be a config option that you could/should set to > avoid this bit of cleverness or nuisance by git-annex..
Here are the permissions: 0755 /tmp/tmp-orgtest/ 0700 /tmp/tmp-orgtest/org-annex-test19785b6F/ 0775 /tmp/tmp-orgtest/org-annex-test19785b6F/.git/ 0775 /tmp/tmp-orgtest/org-annex-test19785b6F/.git/annex/ 0775 /tmp/tmp-orgtest/org-annex-test19785b6F/.git/annex/objects/ 0775 /tmp/tmp-orgtest/org-annex-test19785b6F/.git/annex/objects/jm/ 0775 /tmp/tmp-orgtest/org-annex-test19785b6F/.git/annex/objects/jm/P2/ 0555 /tmp/tmp-orgtest/org-annex-test19785b6F/.git/annex/objects/jm/P2/SHA256E-s12--a948904f2f0f479b8f8197694b30184b0d2ed1c1cd2a1ec0fb85d299a192a447/ 0444 /tmp/tmp-orgtest/org-annex-test19785b6F/.git/annex/objects/jm/P2/SHA256E-s12--a948904f2f0f479b8f8197694b30184b0d2ed1c1cd2a1ec0fb85d299a192a447/SHA256E-s12--a948904f2f0f479b8f8197694b30184b0d2ed1c1cd2a1ec0fb85d299a192a447 I presume this is to maintain the integrity of the file contents in the repository. It would be possible to drop these files after the test (using git annex drop --force), but if something goes wrong there the rm -rf would not clean up the test directory properly. If you think that is a better solution I can do that. best, Erik
