I've run into a strange situation with git lately. It seems that
anything I do involving git will alter the permissions on my index
file to the point that I can't do anything until I re-add the
permissions on the file.
Looks like a bug to me, is it? It does seem like this has started
happening since I moved over to 64b Ubuntu.
$ ll .git
total 156K
...
drwxrwxrwx 2 dev dev 4.0K Jul 23 09:30 hooks
-rwxrwxrwx 1 dev dev 17K Aug 8 13:12 index
drwxrwxrwx 2 dev dev 4.0K Jul 19 09:31 info
...
$ gs
# On branch build-0.3
# Your branch is ahead of 'staging/build-0.3' by 5 commits.
# (use "git push" to publish your local commits)
#
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# scripts/loadMongo.coffee
nothing added to commit but untracked files present (use "git add" to track)
$ ll .git
total 156K
...
drwxrwxrwx 2 dev dev 4.0K Jul 23 09:30 hooks
-rw-rw-r-- 1 dev dev 17K Aug 8 13:16 index # <---------------
this line <-------------------------------
drwxrwxrwx 2 dev dev 4.0K Jul 19 09:31 info
...
$ git --version
git version 1.8.3.4
Ubuntu:
Distributor ID: Ubuntu
Description: Ubuntu 12.04.2 LTS
Release: 12.04
Codename: precise
From: Stefan Beller <hidden> Date: 2016-06-15 22:58:22
On 08/08/2013 10:27 PM, Justin Collum wrote:
I've run into a strange situation with git lately. It seems that
anything I do involving git will alter the permissions on my index
file to the point that I can't do anything until I re-add the
permissions on the file.
Looks like a bug to me, is it? It does seem like this has started
happening since I moved over to 64b Ubuntu.
$ ll .git
total 156K
...
drwxrwxrwx 2 dev dev 4.0K Jul 23 09:30 hooks
-rwxrwxrwx 1 dev dev 17K Aug 8 13:12 index
drwxrwxrwx 2 dev dev 4.0K Jul 19 09:31 info
...
$ gs
# On branch build-0.3
# Your branch is ahead of 'staging/build-0.3' by 5 commits.
# (use "git push" to publish your local commits)
#
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# scripts/loadMongo.coffee
nothing added to commit but untracked files present (use "git add" to track)
$ ll .git
total 156K
...
drwxrwxrwx 2 dev dev 4.0K Jul 23 09:30 hooks
-rw-rw-r-- 1 dev dev 17K Aug 8 13:16 index # <---------------
this line <-------------------------------
drwxrwxrwx 2 dev dev 4.0K Jul 19 09:31 info
...
$ git --version
git version 1.8.3.4
Ubuntu:
Distributor ID: Ubuntu
Description: Ubuntu 12.04.2 LTS
Release: 12.04
Codename: precise
The permissions are set to reading for all and writing for you(r user)
and your group. This should be no problem with standard git commands.
Before you had the index file executable, why would you need that?
What kind of filesystem do you have? (The output of 'mount' would be
interesting)
Also what exactly breaks? ("can't do anything")
What commands do not behave as you'd expect?
Stefan
From: Andrew Ruder <hidden> Date: 2016-06-15 22:58:22
On Thu, Aug 08, 2013 at 11:35:35PM +0200, Stefan Beller wrote:
On 08/08/2013 10:27 PM, Justin Collum wrote:
quoted
[...]
-rwxrwxrwx 1 dev dev 17K Aug 8 13:12 index
[...]
-rw-rw-r-- 1 dev dev 17K Aug 8 13:16 index # <---------------
The permissions are set to reading for all and writing for you(r user)
and your group. This should be no problem with standard git commands.
Before you had the index file executable, why would you need that?
I'm about 90% sure the issue he's having is that the write bit for
other/world goes away and he is neither the user dev or the group dev
and the reason for all the executable bits is that he is regularly
running
chmod -R 777 .
Justin, if this is true, I will tell you that git respects your umask
but I just can't bring myself to really suggest someone type umask 000
ever. :(
- Andy
On Thu, Aug 8, 2013 at 3:18 PM, Andrew Ruder [off-list ref] wrote:
he is neither the user dev or the group dev
I am both. There's only one user on this machine and he is me.
he is regularly running chmod -R 777
Yes, true. I have a program that I use to edit some of these files
(not the git files) that likes to screw up permissions. It's a long
story. Anyway, I've been running that chmod regularly since well
before this git issue started. I'll start using 644 for the chmod and
see if that helps.
From: Kyle J. McKay <hidden> Date: 2016-06-15 22:58:22
On Aug 8, 2013, at 15:18, Andrew Ruder wrote:
On Thu, Aug 08, 2013 at 11:35:35PM +0200, Stefan Beller wrote:
quoted
On 08/08/2013 10:27 PM, Justin Collum wrote:
quoted
[...]
-rwxrwxrwx 1 dev dev 17K Aug 8 13:12 index
[...]
-rw-rw-r-- 1 dev dev 17K Aug 8 13:16 index # <---------------
The permissions are set to reading for all and writing for you(r
user)
and your group. This should be no problem with standard git commands.
Before you had the index file executable, why would you need that?
I'm about 90% sure the issue he's having is that the write bit for
other/world goes away and he is neither the user dev or the group dev
and the reason for all the executable bits is that he is regularly
running
chmod -R 777 .
Justin, if this is true, I will tell you that git respects your umask
but I just can't bring myself to really suggest someone type umask 000
ever. :(
Justin,
If you really want a repository that's writable by everyone, why not
just do "git config core.sharedRepository 0666" ?
If you just want them to be group-writable you may be happier with
"git config core.sharedRepository true" or possibly "git config
core.sharedRepository all". The setting is described fully in "git
help config".
From: Andrew Ruder <hidden> Date: 2016-06-15 22:58:22
On Thu, Aug 08, 2013 at 03:33:32PM -0700, Justin Collum wrote:
On Thu, Aug 8, 2013 at 3:18 PM, Andrew Ruder [off-list ref] wrote:
quoted
he is neither the user dev or the group dev
I am both. There's only one user on this machine and he is me.
If you are running as 'dev', then I'm not sure how the permissions in
the modified case would affect git's ability to work with the file.
Seems like everything should be working fine... what is the error you
get when things stop working?
doing
sudo chmod 644 ./.git/index
instead of 777 resulted in the same result a bit later:
$ gs
fatal: index file open failed: Permission denied
On Thu, Aug 8, 2013 at 3:37 PM, Kyle J. McKay [off-list ref] wrote:
On Aug 8, 2013, at 15:18, Andrew Ruder wrote:
quoted
On Thu, Aug 08, 2013 at 11:35:35PM +0200, Stefan Beller wrote:
quoted
On 08/08/2013 10:27 PM, Justin Collum wrote:
quoted
[...]
-rwxrwxrwx 1 dev dev 17K Aug 8 13:12 index
[...]
-rw-rw-r-- 1 dev dev 17K Aug 8 13:16 index # <---------------
The permissions are set to reading for all and writing for you(r user)
and your group. This should be no problem with standard git commands.
Before you had the index file executable, why would you need that?
I'm about 90% sure the issue he's having is that the write bit for
other/world goes away and he is neither the user dev or the group dev
and the reason for all the executable bits is that he is regularly
running
chmod -R 777 .
Justin, if this is true, I will tell you that git respects your umask
but I just can't bring myself to really suggest someone type umask 000
ever. :(
Justin,
If you really want a repository that's writable by everyone, why not just do
"git config core.sharedRepository 0666" ?
If you just want them to be group-writable you may be happier with "git
config core.sharedRepository true" or possibly "git config
core.sharedRepository all". The setting is described fully in "git help
config".