insufficient permission for adding an object to repository database objects

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 [e-mail]:########/###-distribution.git
 ! [remote rejected] TSMETA-81-COMMON -> TSMETA-81-COMMON (unpacker error)
error: failed to push some refs to '[e-mail]:########/###-distribution.git'

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.

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

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

Having the same problem here as well. Seems to be related to https://bitbucket.org/site/master/issue/6731/unable-to-push-objects-to-git-repo (ping @Erik van Zijst)

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.

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.

I've just got this issue as well, with a private repo. Was working fine to the same repo/branch 2 hours ago.

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.

Same thing as @Benedikt Kristinsson Forchhammer

It just seems to be my account, and it persists even by cloning the repository.

Best,

Guillem

Workaround is to clone the repository under the alternate protocol to the one you are using (eg HTTPS instead of SSL).

'insufficient permission for adding an object to repository database objects' ain't a country I ever heard of.

Same problem here. Some developers can push branches, others can't. Is there a fix in sight?

Same problem here

We're delaying a deploy because of this error. Is anyone going to fix it??

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... ;-)

Same problem here: please fix!

Same problem here.

Deffinitely blocker. Same here.

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 [e-mail]:{git file} ! [remote rejected] {branch name} -> {branch name} (unpacker error) error: failed to push some refs to '[e-mail]:{git file}'

Same here. Not sure how to resolve this. You think Bitbucket might jump in sometime soon and perhaps explain how to proceed here?

let's flipping hope so. this is holding back a lot of developers here.

Same problem here: please fix!

I use HTTPS protocol as workaround.

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!

A friend sent me a link: http://blog.shamess.info/2011/05/06/remote-rejected-na-unpacker-error/

@Atlassian Bitbucket Maybe this is the solution?

Same problem here ...

same here

same here

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.

same here

Same here; switching to HTTPS works, but I prefer sticking to ssh keys.

Moved to Github, sooooo happy. Only a second:

git remote set-url origin [e-mail]:username/repository.git

same problem here :(

Also seeing this issue on a private repo. HTTPS workaround is getting me by for now but really hoping we'll see a fix soon...

This is how i resolved the issue for now:

git remote set-url origin https://[USERNAME]@bitbucket.org/[YOUR-REPO].git

It seems, at least in my case, that after pushing some changes via HTTPS I can now push via SSH as usual.

Same here.

Same here. Please fix.

The https work-around worked for me.

git remote set-url origin https://[e-mail]/_my_/_repo_.git
git pull
git push
git remote set-url origin [e-mail]:_my_/_repo_.git

Ron's steps fixed it for me.

I wish I had searched this last night. Spent way too much time on stack overflow trying to fix the error.

Ron's above work-around also fixed it for us. Thanks!

Same problem here. HTTPS protocol fixed the problem.

same here

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.

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

If urgent please contact MessageXchange Support: [e-mail] - otherwise I will respond when I return.

Multiple teams here are having this issue as well.

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 [e-mail] with any broken repositories if you cannot wait.

Same here...

experiencing the same issue as well..

Issue #11035 was marked as a duplicate of this issue.

Issue #11029 was marked as a duplicate of this issue.

@Jarad DeLorenzo Thank you! The workaround worked for me.

Me too. Thanks!

Thanks @Jarad DeLorenzo , your temporary workaround did the trick for me ... https://bitbucket.org/site/master/issue/11026/insufficient-permission-for-adding-an#comment-15924178

Same here... thinking more and more to move to GitHub...

Emailed support directly and told them the repo that needed attention. They fixed it right up.

Same issue here :(

Same issue here, but I used https instead of ssh and works fine for me. :D

Now its working for me!!! It seems that was fixed.

Cheers and thank you for the support!!

Still broken for me on ssh. Can we have an ETA on the fix please?

Same here, anyone please fix that grrrr

Working for me now. Thanks

Issue is now resolved for me.

Works for me

mailed @ [e-mail] and they fixed it within no time

Also working for me. Thanks!

Thanks for your patience! This should be fixed now. If you are still having trouble, please contact [e-mail] so we can further troubleshoot the issue.

Issue #11028 was marked as a duplicate of this issue.

Issue #11034 was marked as a duplicate of this issue.

@Kaleb Elwert We're also experiencing the same issue. I'm trying to send an email to [e-mail] but for some reason it is failing:

Delivery to the following recipient failed permanently:

[e-mail]

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?

@basco.johnkevin You can also file an issue on https://support.atlassian.com. If you still have trouble, let me know and we'll work something out.

@Kaleb Elwert Yeah we're still experiencing the same issue. I sent you a message, please check it. Thanks!

@Kaleb Elwert Have you had the chance to look at the message I sent to you yesterday? We really need the issue to be fixed asap.

This problem just came back for me today. This is the 3rd time.

It appears to happen every time I do a merge.

@Julian Paas Could you please file an issue by emailing [e-mail] or at https://support.atlassian.com? We'd be happy to help resolve this, but we try to avoid passing personal information over a public issue tracker.

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

I am getting similar error. What is the solution?

any solution ? any link where the solution given ?