I also got this message yesterday once. I deleted my local copy of the branch I was pushing, then pulled it, made my changes and then pushed it fine.
A quick google indicates this is likely an issue with bitbucket being screwed up https://bitbucket.org/site/master/issue/11029/remote-error-insufficient-permission-for What is our backup plan for when bitbucket starts to suck? Barry > On Feb 25, 2015, at 8:28 AM, Matthew Knepley <[email protected]> wrote: > > knepley/feature-harmonic-advection *$:/PETSc3/petsc/petsc-dev$ git push > git push > Counting objects: 149, done. > Delta compression using up to 4 threads. > Compressing objects: 100% (35/35), done. > Writing objects: 100% (35/35), 4.60 KiB | 0 bytes/s, done. > Total 35 (delta 30), 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 [email protected]:petsc/petsc > ! [remote rejected] knepley/feature-harmonic-advection -> > knepley/feature-harmonic-advection (unpacker error) > error: failed to push some refs to '[email protected]:petsc/petsc' > > > Matt > > -- > What most experimenters take for granted before they begin their experiments > is infinitely more interesting than any results to which their experiments > lead. > -- Norbert Wiener
