git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luciano Rocha <luciano@eurotux.com>
To: Dominic Rose <dominic@bioinf.uni-leipzig.de>
Cc: git@vger.kernel.org
Subject: Re: error: insufficient permission
Date: Mon, 21 Sep 2009 09:52:21 +0100	[thread overview]
Message-ID: <20090921085221.GA4931@bit.office.eurotux.com> (raw)
In-Reply-To: <4AB73A07.3020703@bioinf.uni-leipzig.de>

[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]

On Mon, Sep 21, 2009 at 10:32:07AM +0200, Dominic Rose wrote:
> Hi,
> 
> may please somebody help me with the following issue. I try to
> checkin changes to a repository I created. Seems like I have some
> permission problems, but I can't figure out whats going wrong:
> 
> $ git commit -m 'test'
> Created commit 07b3a4a: test
> 1 files changed, 1 insertions(+), 1 deletions(-)
> $ git push
> Counting objects: 8, done.
> Compressing objects: 100% (6/6), done.
> Writing objects: 100% (6/6), 1.56 KiB, done.
> Total 6 (delta 4), reused 0 (delta 0)
> error: insufficient permission for adding an object to repository
> database ./objects
> 
> fatal: failed to write object
> error: unpack failed: unpacker exited with error code
> To /homes/[...]
> ! [remote rejected] master -> master (n/a (unpacker error))
> error: failed to push some refs to '/homes/[...]'

That's a filesystem permissions problem on the server side. You'll have
to check if your user has permissions to write to the objects subdir of the
repository.

-- 
Luciano Rocha <luciano@eurotux.com>
Eurotux Informática, S.A. <http://www.eurotux.com/>

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-09-21  8:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21  8:32 error: insufficient permission Dominic Rose
2009-09-21  8:52 ` Luciano Rocha [this message]
2009-09-21  8:53 ` Johannes Sixt
2011-12-16  8:09 ` Manish Patel

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=20090921085221.GA4931@bit.office.eurotux.com \
    --to=luciano@eurotux.com \
    --cc=dominic@bioinf.uni-leipzig.de \
    --cc=git@vger.kernel.org \
    /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).