| Summary: | Paho Python repo needs history squashing | ||
|---|---|---|---|
| Product: | Community | Reporter: | Roger Light <roger> |
| Component: | Git | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | denis.roy, thanh.ha, wayne.beaton |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Roger Light
Roger, I've given you "Force Push" and "Forge Committer" rights. This should be enough to allow you to force push a new master branch. Please let us know when you've done the push so that I can revert these permissions. I've tried to do a force push using the gerrit url, it failed with: remote: error: The author does not have a Gerrit account. remote: All authors must either be a commiter on the project, or have a current CLA on file. This is on a commit from Jan-Piet Mens, who has a CLA on record, used a proper commit message and the push was fine when it was done - although this was prior to moving to gerrit. Can you advise how I should proceed? (In reply to Roger Light from comment #2) > I've tried to do a force push using the gerrit url, it failed with: > > remote: error: The author does not have a Gerrit account. > remote: All authors must either be a commiter on the project, or have a > current CLA on file. > > This is on a commit from Jan-Piet Mens, who has a CLA on record, used a > proper commit message and the push was fine when it was done - although this > was prior to moving to gerrit. > > Can you advise how I should proceed? Right that's a problem. We can work around this by not using Gerrit Push URLs. I've re-enabled the old URLs for this repo so you can push to the old URLs again. This will mess up Gerrit permissions but we can fix it after you finish your push. Use this URL: ssh://git.eclipse.org/gitroot/paho/org.eclipse.paho.mqtt.python.git If Jan hasn't logged into Gerrit at least once, then Gerrit doesn't know who that person is. Logging in once may just solve the problem. (In reply to Denis Roy from comment #4) > If Jan hasn't logged into Gerrit at least once, then Gerrit doesn't know who > that person is. Logging in once may just solve the problem. Right that's true too. I forgot this repo's pretty new. I was thinking that it might have had a long history of commits with authors who are no longer around but if the issue's only with 1 committer having him login will solve the issue. Jan-Piet logged in and I was able to push all of the commits. You can remove the extra permissions now, thanks. (In reply to Roger Light from comment #6) > Jan-Piet logged in and I was able to push all of the commits. > > You can remove the extra permissions now, thanks. Done. |