Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 346923

Summary:	Insufficient permission for adding an object on amp
Product:	Community	Reporter:	Miles Parker <milesparker>
Component:	Git	Assignee:	Eclipse Webmaster <webmaster>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X
Whiteboard:

Description Miles Parker

2011-05-23 22:08:55 EDT

Hi guys,

I'm getting the below error. Up until now I've assumed that it is a tooling issue because everyone says that git can't get corrupted. :) See bug 346140 (if you dare). So I'd held up on bothering you guys about it. But I am seeing that there have been issues, e.g. bug 320452 and it is happening on command-line for me as well, so perhaps it isn't a client thing after all. The maddening aspect is that there doesn't seem to be any pattern but the first few pushes always seem to work. I could clone the same repos right now, make the changes and push them and they'd be likely to work.

The current commit was into org.eclipse.amp/org.eclipse.amp.escape/plugins/org.eclipse.amp.escape.ide but its been happening everywhere. Could you check permissions on the repos objects?

thanks,

Miles

Counting objects: 40, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (16/16), done.
Writing objects: 100% (21/21), 7.03 KiB, done.
Total 21 (delta 11), 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 ssh://mparker@git.eclipse.org/gitroot/amp/org.eclipse.amp.git
 ! [remote rejected] master -> master (n/a (unpacker error))
error: failed to push some refs to 'ssh://mparker@git.eclipse.org/gitroot/amp/org.eclipse.amp.git'

Comment 1 Denis Roy

2011-05-24 15:47:07 EDT

Your repository's config file did not have sharedrepository = 1

Some git clients (such as yours) preserved the filesystem-enforced "group writable" setting -- but jruttima's client was not, and was removing group write permission on specific has directories.

It's all fixed now -- you should be good to go.

Comment 2 Miles Parker

2011-05-24 15:47:58 EDT

Great! Thanks Denis. :)

Comment 3 Miles Parker

2011-05-24 15:48:51 EDT

Oh sorry, is there something we should enforce as a project to prevent this form happening again?

Comment 4 Denis Roy

2011-05-24 15:55:26 EDT

If you create other repos, you need to make sure sharedrepository = 1 is in the config file.  That is all.