All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Uemlianin <ivan@llaisdy.com>
To: Jeff King <peff@peff.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: A sudden lack of permission
Date: Mon, 27 Sep 2010 17:16:43 +0100	[thread overview]
Message-ID: <4CA0C36B.5000708@llaisdy.com> (raw)
In-Reply-To: <20100927160759.GB10256@sigill.intra.peff.net>

  Dear Peff

Thanks for your help.

Yes, I can ssh onto the server, cd to /var/www/git/my_repos.git and add, 
edit files, etc.

There is another person on the box doing sysadmin.  I'll ask.

Is there any reason the repos could have just broken somehow?  A corrupt 
push?

Best wishes

Ivan



On 27/09/2010 17:07, Jeff King wrote:
> On Mon, Sep 27, 2010 at 03:52:52PM +0100, Ivan Uemlianin wrote:
>
>> I have been using git quite happily for a good while, pushing to my
>> remote.  Suddenly this afternoon the remote told me I didn't have
>> permission:
>>
>>      $ git push
>>      ivan@remote.org's password:
>>      Counting objects: 19, done.
>>      Delta compression using up to 2 threads.
>>      Compressing objects: 100% (11/11), done.
>>      Writing objects: 100% (11/11), 1.04 KiB, done.
>>      Total 11 (delta 8), reused 0 (delta 0)
>>      error: insufficient permission for adding an object to repository
>> database ./objects
>>
>>      fatal: failed to write object
>>      error: unpack failed: unpack-objects abnormal exit
>>      To ivan@remote.org:/var/www/git/my_repos.git
>>       ! [remote rejected] master ->  master (n/a (unpacker error))
>>      error: failed to push some refs to
>> 'ivan@remote.org:/var/www/git/my_repos.git'
>>
>> I had sufficient permission even this morning!
>>
>> Please could someone tell me what might have happened and, more
>> importantly, how I can start pushing to the remote again?  The
>> project in my_repos is large, so I'd rather not start a new repos
>> from scratch.
> Presumably the permissions on the server changed for some reason. Can
> you ssh to the remote host and confirm that user "ivan" has permissions
> to write to the repo's objects dir? If not, then you will have to figure
> out what happened, but it is likely outside the scope of git (e.g., an
> overly inclusive chmod by some cron job or admin on the box).
>
> If you do have permissions, then we will have to dig deeper into why git
> would fail, but the permissions would appear fine.
>
> -Peff


-- 
============================================================
Ivan A. Uemlianin
Speech Technology Research and Development

                     ivan@llaisdy.com
                      www.llaisdy.com
                          llaisdy.wordpress.com
                      www.linkedin.com/in/ivanuemlianin

     "Froh, froh! Wie seine Sonnen, seine Sonnen fliegen"
                      (Schiller, Beethoven)
============================================================

  reply	other threads:[~2010-09-27 16:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27 14:52 A sudden lack of permission Ivan Uemlianin
2010-09-27 16:07 ` Jeff King
2010-09-27 16:16   ` Ivan Uemlianin [this message]
2010-09-27 16:22     ` Jeff King
2010-09-27 16:30       ` Ivan Uemlianin

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=4CA0C36B.5000708@llaisdy.com \
    --to=ivan@llaisdy.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.