error: insufficient permission for adding an object to repository database objects

Issue #11028 duplicate
Catalin
created an issue

Hi,

Yesterday git was loading very slow and at some point it failed when trying to push the changes I made to the master branch. Today I can't seem to push any changes to the master branch.

I think because of the failure of yesterday some files got jammed. Can you please do a permissions check on all files for the enjincms (master branch)?

Here's the error it throws:

Pushing to git@bitbucket.org:enjineer/enjincms.git remote: error: insufficient permission for adding an object to repository database objects remote: fatal: failed to write object error: unpack failed: unpack-objects abnormal exit To git@bitbucket.org:enjineer/enjincms.git ! [remote rejected] master -> master (unpacker error) error: failed to push some refs to 'git@bitbucket.org:enjineer/enjincms.git'

Comments (11)

  1. Adam Zegelin

    We're seeing the same error:

    remote: error: insufficient permission for adding an object to repository database objects        
    remote: fatal: failed to write object        
    error: unpack failed: unpack-objects abnormal exit
    
  2. Bartosz Grzybowski

    Same error here

    remote: error: insufficient permission for adding an object to repository database objects
    remote: fatal: failed to write object
    error: unpack failed: unpack-objects abnormal exit
    
  3. Anonymous

    Me too!

    remote: error: insufficient permission for adding an object to repository database objects
    remote: fatal: failed to write object
    error: unpack failed: unpack-objects abnormal exit
    
  4. Nathan Racklyeft

    Same problem here.

    remote: error: insufficient permission for adding an object to repository database objects
    remote: fatal: failed to write object
    error: unpack failed: unpack-objects abnormal exit
    
  5. Kaleb Elwert

    Thanks for your patience! This should be fixed now. If you are still having trouble, please contact support@bitbucket.org so we can further troubleshoot the issue.

  6. Log in to comment