insufficient permission for adding an object to repository database objects

Issue #11026 resolved
Tarrant Marshall
created an issue

Latest commit has stopped me from pushing this branch to Bit Bucket. If I merge this particular commit into any other branches, it also buggers up that branch from pushing.

# git push origin TSMETA-81-COMMON
Counting objects: 23, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (13/13), done.
Writing objects: 100% (13/13), 5.00 KiB, done.
Total 13 (delta 9), reused 0 (delta 0)
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:########/###-distribution.git
 ! [remote rejected] TSMETA-81-COMMON -> TSMETA-81-COMMON (unpacker error)
error: failed to push some refs to 'git@bitbucket.org:########/###-distribution.git'

Comments (80)

  1. Daniel Bowen

    I'm seeing the same error here, just in the last few hours on one specific branch. Others on my team are able to push okay, and I can push another branch up okay.

  2. 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
    
  3. Guillem Vidal Cantavella

    I am seeing the same error also

    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. Estanislau Trepat

    I see the same here. As others have said, other branches push ok, but one in particular does not ¿?.

    EDIT: Re-cloning the repo, produces the exact same results when you checkout the branch & try to push again.

  5. Benedikt Forchhammer

    I have the same problem with a private repository. I cannot push any branches to that repository, but other repositories work fine. Colleagues can push fine as well, it seems to be just my account.

  6. yair even or

    bitbucket really fucked things up this time, since yesterday everything works very slow and of today, I get this error. I will be moving to a different company after such a screw up. we have production servers that needs updating and this holds us back. the company supply no explanation in it's website.

    not professional.

  7. Benedikt Forchhammer

    I found out that for me it is actually just one specific (one-line) change which is not accepted. Other changes still work fine. It was tedious to figure out, but I managed to continue work by modifying/not committing that one change... ;-)

  8. David Vartanian

    This is my last try a minute ago:

    Counting objects: 37, done. Delta compression using up to 4 threads. Compressing objects: 100% (15/15), done. Writing objects: 100% (15/15), 1.49 KiB, done. Total 15 (delta 11), reused 0 (delta 0) 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:{git file} ! [remote rejected] {branch name} -> {branch name} (unpacker error) error: failed to push some refs to 'git@bitbucket.org:{git file}'

  9. Sam Dods

    quite right @Masahiko MURAKAMI, but @awong_digitaltomato suggests cloning the repo again under using HTTPS, which is unnecessary.

    it's much simpler to just add a new remote pointing to the HTTPS URL for the repo, and then ensure you always push to the HTTPS remote.

    no need to make another clone!

  10. Brad Gross

    We've ben seeing this since last night:

    Delta compression using up to 8 threads. Compressing objects: 100% (89/89), done. Writing objects: 100% (96/96), 43.40 KiB | 0 bytes/s, done. Total 96 (delta 57), reused 0 (delta 0) 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

    Cloning the branch again with HTTPS works but it would still be beneficial for this issue to be resolved so we can avoid the confusion of always having to specify the remote.

  11. Ron Lussier

    The https work-around worked for me.

    git remote set-url origin https://_username_@bitbucket.org/_my_/_repo_.git
    git pull
    git push
    git remote set-url origin git@bitbucket.org:_my_/_repo_.git
    
  12. Kevin Meixner

    I have had the same problem occur twice today. The first time I just re-cloned the repository and it worked for a while but then stopped working throwing the same error later. I then tried Ron Lussier's work-around above and so far so good it is working.

  13. Daniel Bowen

    Hi, I'm on leave from Thursday 26/2/2015.

    If urgent please contact MessageXchange Support: support@messagexchange.com - otherwise I will respond when I return.

  14. Kaleb Elwert

    Hello! Sorry for the delay in responding to this. This was a side-effect of yesterday's maintenance. We have since corrected the mistake and are working on resolving all issues.

    Feel free to contact support by emailing support@bitbucket.org with any broken repositories if you cannot wait.

  15. basco.johnkevin

    @Kaleb Elwert We're also experiencing the same issue. I'm trying to send an email to support@bitbucket.org but for some reason it is failing:

    Delivery to the following recipient failed permanently:

    support@bitbucket.org

    Technical details of permanent failure: Message rejected by Google Groups. Please visit http://mail.google.com/support/bin/answer.py?hl=en&answer=188131 to review our Bulk Email Senders Guidelines.

    Is there any other email address where I can send an email?

  16. Geranne Riego

    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

  17. Log in to comment