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

Re: Fatal: <hash> is corrupted can be caused by wrong permissions

From
Jeff King <peff@peff.net>
Date
Oct 25, 2014, 10:17 UTC
Message-ID
<20141025101741.GA17058@peff.net>
In-Reply-To
<vpqbnp1zhp7.fsf@anie.imag.fr>
On Fri, Oct 24, 2014 at 04:05:24PM +0200, Matthieu Moy wrote:
Show 7 quoted lines
> I can reproduce with Git 1.7.10 by doing a chmod 0 on some object files,
> but recent Git's produce
> 
> Checking object directories: 100% (256/256), done.
> fatal: failed to read object ab2e06e74d922268fbff8d219dad9eee63786947: Permission denied
> 
> So I guess this has already been fixed :-).

Probably d6c8a05 (open_sha1_file: report "most interesting" errno, 2014-05-15). The example in the commit message even uses "chmod 0". :)

It's in v2.0.1.
-Peff
Previous: Matthieu Moy
Message 3 of 3 in “Fatal: <hash> is corrupted can be caused by wrong permissions”
  1. R. David MurrayOct 24, 2014
  2. Matthieu MoyOct 24, 2014
  3. Jeff KingOct 25, 2014

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.