我第一次上传到github，我遇到以下问题：
dan@dan-netbook:/opt/lampp/htdocs/myProject$ git push origin master
error: unable to create directory for .git/refs/remotes/origin/master
error: Cannot lock the ref 'refs/remotes/origin/master'.
Everything up-to-date
我按照github.com上的说明收到此错误。是否有人熟悉此类错误？
使用sudo运行命令返回：
Permission denied (publickey).
fatal: The remote end hung up unexpectedly
正在运行 - ssh -v git@github.com返回：
OpenSSH_5.1p1 Debian-6ubuntu2, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to github.com [207.97.227.239] port 22.
debug1: Connection established.
debug1: identity file /home/dan/.ssh/identity type -1
debug1: identity file /home/dan/.ssh/id_rsa type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: identity file /home/dan/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 Debian-5github2
debug1: match: OpenSSH_5.1p1 Debian-5github2 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.1p1 Debian-6ubuntu2
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'github.com' is known and matches the RSA host key.
debug1: Found key in /home/dan/.ssh/known_hosts:3
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /home/dan/.ssh/id_rsa
debug1: Remote: Forced command: gerve danwoods
debug1: Remote: Port forwarding disabled.
debug1: Remote: X11 forwarding disabled.
debug1: Remote: Agent forwarding disabled.
debug1: Remote: Pty allocation disabled.
debug1: Server accepts key: pkalg ssh-rsa blen 277
debug1: Remote: Forced command: gerve danwoods
debug1: Remote: Port forwarding disabled.
debug1: Remote: X11 forwarding disabled.
debug1: Remote: Agent forwarding disabled.
debug1: Remote: Pty allocation disabled.
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
PTY allocation request failed on channel 0
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
ERROR: Hi danwoods! You've successfully authenticated, but GitHub does not provide shell access
debug1: channel 0: free: client-session, nchannels 1
Connection to github.com closed.
Transferred: sent 2576, received 2904 bytes, in 1.8 seconds
Bytes per second: sent 1469.6, received 1656.7
debug1: Exit status 1
答案 0 :(得分：13)
看起来您有本地权限问题。关于这个问题，Git没有具体的内容。层次结构可以包含任何内容，这些指令将完全相同。默认情况下，Git将遵循稍后描述的umask设置（除非它被 core.sharedRepository 配置覆盖）。
在您的评论中，您说您的用户将是更新层次结构内容的用户，您还将拥有一个将读取层次结构内容的Web服务器。我将假设Web服务器在其他用户下运行（通常情况就是如此（例如，Apache以用户 httpd 运行））。此外，我认为如果同一台机器上的其他用户也可以读取层次结构的内容，这是可以接受的（这种配置所需的权限方案更复杂 - 它涉及使用特殊组并确保您的文件和目录具有该群体作为他们的“群组拥有者”）。
使 dan 成为所有层次结构的所有者。
任何可以“sudo to root”（或在没有 sudo 的情况下在root shell中运行）的用户：
someuser$ sudo chown -R dan /opt/lammp/htdocs/myProject
授予每个人读取权限（并且还对所有目录和所有已经可由某人执行的文件执行权限;剥离任何写入权限）。此外，请提供 dan 写入权限。
正如 dan （请注意缺少 sudo ！）：
dan$ chmod -R a-st=rX,u+w /opt/lammp/htdocs/myProject
这将剥离setuid / setgid / sticky位并给出目录和可执行文件模式755以及所有其他文件模式644。
要确保其他人（例如Web服务器用户）可以读取新文件但不可写（默认情况下），则应在此目录中设置umask。
dan$ umask 022
这会掩盖新文件和目录的“组”和“其他”写入权限，但不会单独读取和执行。
如果你忘了使用它，你的默认umask限制性更强（或限制性更小），那么你需要重新运行（非 sudo ！） chmod 来自“初始设置”部分的命令。它将重置任何过于严格（或太松散）的权限。