Git: unable to click from one computer

Question

One of my colleagues has a problem pushing changes to git on his machine. If he enters another car, he can press hard, but from his car, when he tries to press, he gets the following error.

     D: \ Projects \ test1 \ best-practices> git push
     Counting objects: 4, done.
     Compressing objects: 100% (2/2), done.
     Writing objects: 100% (3/3), 273 bytes, done.
     Total 3 (delta 1), reused 0 (delta 0)
     error: unable to create temporary sha1 filename ./objects/42: Permission denied

     fatal: failed to write object
     error: unpack failed: unpacker exited with error code
     To //civ3s012/gitrepos/best-practices/.git
      !  [remote rejected] master -> master (n / a (unpacker error))
     error: failed to push some refs to '//civ3s012/gitrepos/best-practices/.git'

A server is a Windows machine, just like a client. Someone else does not have this problem - it seems that this is a problem with server permissions, but we decided as much as possible. In addition, the fact that he can log in to another machine and click using the same username makes him look like not server permissions. Any ideas what might be wrong here?

Answer 1

I am not a Windows user, so I'm a little sticking in the dark. It looks like the remote file system is mounted and you just click on it (without using ssh: // or git: //). Is this FS somehow mounted? Can it create / modify files there (outside of git )?

Answer 2

Try adding this configuration variable to the remote repository:

  $ git config core.sharedRepository "all" $ git config receive.denyNonFastForwards True 

They are usually set with the --shared option in git init when the repo is configured.

I don’t know how Windows permissions interact, so I’m not sure what this solution is. But I know that sometimes a linux user can create files with permissions that cannot be deleted remotely in Git this way. This happened when they belong to the corresponding group, but do not have it as the main group. Setting up a repo exchange on all get around this.

This is similar to collaborative repositioning imported from SVN or CVS.

Answer 3

I know this is a simple answer to a hibernate sleeping answer, but have you confirmed that its hard drive is not full?

Answer 4

The problem was saving the password for this resource, which allowed read access, but not write access. Even when we explicitly installed the drive with the corresponding username and password, the saved password should have been used in the background, which made tracking difficult. To clear the password, we went to the control panel, user accounts, clicked "Advanced", "Password Management" and deleted the login information for this server. After that, everything worked as it should. I accept Pat Notz's answer, as it eventually became FS read-only. Thank!

Answer 5

Perhaps he created a branch in his local repo that already exists on the server, and this ref cannot be updated because it was created by someone else?

Answer 6

Another brain dead answer. Do you have read permissions for these files? It happened to me several times when I mistakenly made changes as another user. Then I can not push. Chown is your friend.