Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368400 - Can't push to new EMF repository
Summary: Can't push to new EMF repository
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Git (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-11 17:22 EST by Kenn Hussey CLA
Modified: 2012-01-12 10:23 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kenn Hussey CLA 2012-01-11 17:22:59 EST 
I just tried to push some changes to the R2_7_maintenance branch of the new EMF repository using the following push URL:

ssh://khussey@git.eclipse.org/gitroot/emf/org.eclipse.emf.git

and got this error:

An internal Exception occurred during push: ssh://khussey@git.eclipse.org/gitroot/emf/org.eclipse.emf.git: error occurred during unpacking on the remote end: unpack-objects abnormal exit

Please advise.
Comment 1 Kenn Hussey CLA 2012-01-12 09:08:29 EST 
I need this to work in order to get the SR2 RC1 build out on time...
Comment 2 Denis Roy CLA 2012-01-12 09:26:19 EST 
Are you using Egit?  If so, which version?  Command line?  Which version?  What are you trying to push.

Need info  :)
Comment 3 Kenn Hussey CLA 2012-01-12 09:34:06 EST 
Eclipse EGit  1.1.0.201109151100-r
Comment 4 Denis Roy CLA 2012-01-12 09:35:15 EST 
Two issues were found with the repo:

1. the group owner was a group that no longer exists.  I've changed it to modeling.emf.emf

2. the repo's config didn't contain "sharedrepository = 1" so new objects didn't necessarily have group-writable perms

I've fixed both of these issues; feel free to try again.
Comment 5 Kenn Hussey CLA 2012-01-12 10:23:29 EST 
(In reply to comment #4)
> I've fixed both of these issues; feel free to try again.

Thanks, works now.