Bug#729757: Does not set permissions on .git/annex according to core.sharedRepository

2014-05-28 Thread martin f krafft
also sprach Joey Hess jo...@debian.org [2014-04-20 22:04 +0200]: I still don't understand what this bug report is about. Let's try again: *** SETUP % GIT_DIR=bare.git git --bare init --shared=group Initialized empty shared Git repository in

Bug#729757: Does not set permissions on .git/annex according to core.sharedRepository

2014-04-20 Thread martin f krafft
also sprach Joey Hess jo...@debian.org [2014-04-17 21:20 +0200]: % setfacl -R -m mask::rwX,group:pm:rwX shared.git % setfacl -R -d -m mask::rwX,group:pm:rwX shared.git I don't understand all this ACL stuff[1]. Is this bug report about file permissions, or about ACLs? AFAIK, git's

Bug#729757: Does not set permissions on .git/annex according to core.sharedRepository

2014-04-20 Thread Joey Hess
martin f krafft wrote: Yes, rsync/cp are enforcing the mode/ownership/group membership/ACL data from the source onto the destination, which I don't think they should. git-annex lets rsync/cp preserve as much of the file metadata is they can, which is generally considered a good thing, and then

Bug#729757: Does not set permissions on .git/annex according to core.sharedRepository

2014-04-20 Thread martin f krafft
also sprach Joey Hess jo...@debian.org [2014-04-20 19:37 +0200]: AFAIK, git-annex has good reasons to use the permissions it uses for objects directories. They seem to be according to umask, not according to core.sharedRepository, which is inconsistent if git-annex changes the permissions of

Bug#729757: Does not set permissions on .git/annex according to core.sharedRepository

2014-04-20 Thread Joey Hess
martin f krafft wrote: also sprach Joey Hess jo...@debian.org [2014-04-20 19:37 +0200]: AFAIK, git-annex has good reasons to use the permissions it uses for objects directories. They seem to be according to umask, not according to core.sharedRepository, which is inconsistent if git-annex

Bug#729757: Does not set permissions on .git/annex according to core.sharedRepository

2014-04-17 Thread Joey Hess
% setfacl -R -m mask::rwX,group:pm:rwX shared.git % setfacl -R -d -m mask::rwX,group:pm:rwX shared.git I don't understand all this ACL stuff[1]. Is this bug report about file permissions, or about ACLs? AFAIK, git's core.sharedRepository does not involve ACLs. I am resorting to reading the tea

Bug#729757: Does not set permissions on .git/annex according to core.sharedRepository

2014-04-06 Thread martin f krafft
retitle 729757 Overwrites default group and ACLs on files stored to .git/annex severity 729757 normal found 729757 5.20140405 thanks also sprach martin f krafft madd...@debian.org [2013-11-19 11:18 +0100]: It seems thus that git-annex creates the temporary file in some other way that causes the

Bug#729757: Does not set permissions on .git/annex according to core.sharedRepository

2014-04-06 Thread Joey Hess
It seems that git-annex (or something called by git-annex) creates a file Surely if you have an strace, you know which it is? I don't know, because you have not told me how to reproduce the problem. -- see shy jo signature.asc Description: Digital signature

Bug#729757: Does not set permissions on .git/annex according to core.sharedRepository

2014-04-06 Thread martin f krafft
also sprach Joey Hess jo...@debian.org [2014-04-06 20:02 +0200]: It seems that git-annex (or something called by git-annex) creates a file Surely if you have an strace, you know which it is? I don't know, because you have not told me how to reproduce the problem. Yes, it's in the bug log, but

Bug#729757: Does not set permissions on .git/annex according to core.sharedRepository

2013-11-19 Thread martin f krafft
also sprach Joey Hess jo...@debian.org [2013-11-18 23:21 +0100]: This is because git-annex moves files into the directory, so it is not creating a new file, so the +S has no effect. At some point, git-annex get creates a file. Where does it do that prior to moving? I am doubtful that it would

Bug#729757: Does not set permissions on .git/annex according to core.sharedRepository

2013-11-19 Thread martin f krafft
also sprach martin f krafft madd...@debian.org [2013-11-19 11:11 +0100]: At some point, git-annex get creates a file. Where does it do that prior to moving? strace told me about .git/annex/tmp: % ls -ld .git/annex/tmp drwx--S--- 2 madduck pm 4096 Nov 19 11:14 .git/annex/tmp so it has g+s,

Bug#729757: Does not set permissions on .git/annex according to core.sharedRepository

2013-11-18 Thread Joey Hess
martin f krafft wrote: 1. .git/annex is missing g+rwx 2. .git/annex/** are missing g+x fixed 3. the actual file object in the annex has the wrong group. This is because git-annex moves files into the directory, so it is not creating a new file, so the +S has no effect. I am doubtful

Bug#729757: Does not set permissions on .git/annex according to core.sharedRepository

2013-11-17 Thread martin f krafft
also sprach Joey Hess jo...@debian.org [2013-11-16 23:13 +0100]: I can't reproduce that. Are you sure those didn't exist before you set core.sharedrepository? Yes, I am sure. But I isolated the problem. If umask is set to 007, it works fine. However, if umask is 077, which I have as default,

Bug#729757: Does not set permissions on .git/annex according to core.sharedRepository

2013-11-16 Thread martin f krafft
Package: git-annex Version: 4.20131106 Severity: wishlist Please respect git's core.sharedRepository setting when creating files/directories under .git/annex. For instance, if core.sharedRepository, the files should get g+rwX, but they currently don't. -- System Information: Debian Release:

Bug#729757: Does not set permissions on .git/annex according to core.sharedRepository

2013-11-16 Thread Joey Hess
martin f krafft wrote: Please respect git's core.sharedRepository setting when creating files/directories under .git/annex. For instance, if core.sharedRepository, the files should get g+rwX, but they currently don't. git-annex (4.20130909) unstable; urgency=low * Honor

Bug#729757: Does not set permissions on .git/annex according to core.sharedRepository

2013-11-16 Thread martin f krafft
also sprach Joey Hess jo...@debian.org [2013-11-16 22:29 +0100]: git-annex (4.20130909) unstable; urgency=low * Honor core.sharedrepository when receiving and adding files in direct mode. Is there a particular file you had in mind? I am using 4.20131002~bpo7 and 4.20131106, so both

Bug#729757: Does not set permissions on .git/annex according to core.sharedRepository

2013-11-16 Thread Joey Hess
martin f krafft wrote: I am using 4.20131002~bpo7 and 4.20131106, so both have this. My problem is that the files under .git/annex/objects/XX/YY/SCHEME-…/SCHEME-….JPG have the right rights, but the parent directories don't get any group rights. I can't reproduce that. Are you sure those