git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: error: Unable to append to .git/logs/refs/remotes/origin/master: Permission denied
Date: Wed, 29 Apr 2009 09:32:56 +0200	[thread overview]
Message-ID: <20090429073256.GB22129@elte.hu> (raw)
In-Reply-To: <20090429040719.GA14912@coredump.intra.peff.net>


* Jeff King <peff@peff.net> wrote:

> On Tue, Apr 28, 2009 at 11:29:43PM -0400, Jeff King wrote:
> 
> > Note the repeated use of "hopefully". :) Maybe the earlier 
> > message is too hidden to rely on. We might be able to get by 
> > with checking "errno" for ENOTDIR after trying to lock the ref 
> > and using a different message, but I don't know how portable 
> > that will be.
> 
> Hmm, that actually doesn't work. errno is properly EACCESS in your 
> example, but the D/F problem doesn't actually set errno, since it 
> is git itself, and not a failed syscall, that determines that 
> "foo/bar" is not available because "foo" exists (and git must do 
> it, because "foo" may be a packed ref).
> 
> So I think we would need to simulate the errno setting, like the 
> patch below. That should generate the hint only when it would 
> actually be useful.

it wasnt hard to figure out what's going on. So this was more of a 
FYI, not really a bug report. Maybe if someone tries to pull into a 
read-only repo the same could happen? My particular breakage (of a 
single ref being root-owned - the rest was mingo owned) is atypical 
enough to be ignored.

If there's no easy/clean solution then please ignore my report.

	Ingo

  reply	other threads:[~2009-04-29  7:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28  7:31 error: Unable to append to .git/logs/refs/remotes/origin/master: Permission denied Ingo Molnar
2009-04-29  3:29 ` Jeff King
2009-04-29  4:07   ` Jeff King
2009-04-29  7:32     ` Ingo Molnar [this message]
2009-04-29  8:06       ` Jeff King
2009-05-25 10:37         ` [PATCH 1/2] lock_ref: inform callers of unavailable ref Jeff King
2009-05-25 10:40         ` [PATCH 2/2] fetch: report ref storage DF errors more accurately Jeff King
2009-05-25 22:23           ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090429073256.GB22129@elte.hu \
    --to=mingo@elte.hu \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).