| Summary: | Orion Git Repo is out-of-date and hook is preventing us from repairing it | ||
|---|---|---|---|
| Product: | Community | Reporter: | Simon Kaegi <simon_kaegi> |
| Component: | Git | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | blocker | ||
| Priority: | P3 | CC: | aniefer, bokowski, john.arthorne, Szymon.Brandys, tomasz.zarna |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Simon Kaegi
*** Bug 347752 has been marked as a duplicate of this bug. *** Bumping up the severity. We can't continue pushing changes until it is resolved. I've removed the hook. Please let me know when you're done so I can out it back. (In reply to comment #3) > I've removed the hook. Please let me know when you're done so I can out it > back. Could you do the same thing for org.eclipse.orion.server? I will push the changes. Yes, done. (In reply to comment #3) > I've removed the hook. Please let me know when you're done so I can out it > back. dev.eclipse.org/gitroot/e4/org.eclipse.orion.client.git is now up-to-date. Both repos are fixed. We may close the bug. (In reply to comment #7) > Both repos are fixed. We may close the bug. Could you post up "how" you fixed the repos, since others may encounter similar problems as well? See bug 347763. Thanks! (In reply to comment #8) > (In reply to comment #7) > > Both repos are fixed. We may close the bug. > > Could you post up "how" you fixed the repos, since others may encounter similar > problems as well? See bug 347763. > > Thanks! We had all commits in our local branch 'master'. When you removed the hook, we were able to push them to the repo. (In reply to comment #8) > (In reply to comment #7) > > Both repos are fixed. We may close the bug. > > Could you post up "how" you fixed the repos, since others may encounter similar > problems as well? See bug 347763. > > Thanks! I believe this was just we had local clones that were ahead of the master by a set of commits that came from a bunch of different people. Some of us had pulled shortly before the servers went down, master came back at an older point missing these commits. This is fixed just by pushing the changes to bring the master back up to date. The thing preventing this was the hook enforcing the commiters: >remote: error: git.eclipse.org does not know this committer, >remote: or this is not you: Szymon.Brandys@pl.ibm.com. >remote: error: git.eclipse.org does not know this committer, >remote: or this is not you: malgorzata.tomczyk@pl.ibm.com. >remote: error: git.eclipse.org does not know this committer, >remote: or this is not you: mamacdon@ca.ibm.com. Webmaster / Denis: did you re-enable the hook? I was just able to push someone else's commit which I think this hook should prevent. (In reply to comment #11) > Webmaster / Denis: did you re-enable the hook? I was just able to push someone > else's commit which I think this hook should prevent. sha? |