git/list[1] front-page[2] threads[3] people[4] search[5] about
 

error: Unable to append to .git/logs/refs/remotes/origin/master: Permission denied

From
IMIngo Molnar <mingo@elte.hu>
Date
Apr 28, 2009, 07:31 UTC
Message-ID
<20090428073138.GA9094@elte.hu>

I had a portion of a repo owned by root accidentally, and the next time i pulled as user mingo Git gave me this warning and suggestion:

 aldebaran:~/git> git pull
 error: Unable to append to .git/logs/refs/remotes/origin/master: Permission denied
 From e2:git
  ! 66996ec..95110d7  master     -> origin/master  (unable to update local ref)
  * [new tag]         v1.6.3-rc2 -> v1.6.3-rc2
 error: some local refs could not be updated; try running
  'git remote prune origin' to remove any old, conflicting branches

Obviousy Git cannot update the ref there so the failure is OK, but the git-remote advice it gives is confusing IMHO: the 'git remote prune origin' cannot fix anything. (and it is clear from the fetch permission failure that there's no chance to fix anything here.)

I suspect there are other, more typical failure modes where that advice is useful - just wanted to point out that it's confusing here.

	Ingo
Next: Jeff King
Message 1 of 8 in “error: Unable to append to .git/logs/refs/remotes/origin/master: Permission denied”
  1. Ingo MolnarApr 28, 2009
  2. Jeff KingApr 29, 2009
  3. Jeff KingApr 29, 2009
  4. Ingo MolnarApr 29, 2009
  5. Jeff KingApr 29, 2009
  6. 1/2 lock_ref: inform callers of unavailable refJeff King, May 25, 2009
  7. 2/2 fetch: report ref storage DF errors more accuratelyJeff King, May 25, 2009
  8. Junio C HamanoMay 25, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.