My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 1842: git push refs/meta/config error mismatched committer email
7 people starred this issue and may be notified of changes. Back to list
Status:  Submitted
Owner:  sop@google.com
Closed:  Mar 2013


Sign in to add a comment
 
Reported by di...@google.com, Mar 22, 2013
Affected Version: 2.6rc0 (2.5.2 too)

What steps will reproduce the problem?
Try to push a refs/meta/config update after having done a change to it from the UI (so the parent commit committer is whatever the Gerrit user ID is on the server).

What is the expected output? What do you see instead?
Should work fine. Instead it complains about the parent commit that the "committer" value does not match my registered emails for my Gerrit user account. Of course it doesn't if the parent commit was done by an update through the Gerrit UI but it shouldn't be checking it.


Please provide any additional information below.
$ git push remote-repo HEAD:refs/meta/config
Counting objects: 5, done.
Delta compression using up to 12 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 438 bytes, done.
Total 3 (delta 1), reused 0 (delta 0)
remote: Resolving deltas: 100% (1/1)
remote: Processing changes: refs: 1, done    
remote: (W) 21e9896: commit subject >65 characters; use shorter first paragraph
remote: (W) 21e9896: commit message lines >70 characters; manually wrap lines
remote: 
remote: ERROR:  In commit ef589427a65ed7240cbad436439b3dd487174a83
remote: ERROR:  committer email address server-gerrit-commits@example.com
remote: ERROR:  does not match your user account.
remote: ERROR:
remote: ERROR:  The following addresses are currently registered:
remote: ERROR:    me@example.com
remote: ERROR:
remote: ERROR:  To register an email address, please visit:
remote: ERROR:  https:/server/#/settings/contac
remote: 
remote: 
To remote-repo
 ! [remote rejected] HEAD -> refs/meta/config (invalid committer)

Adding a Forge Committer Identity ACL on refs/meta/config workarounds the problem.

Currently I have the following ACLs in All-Projects:
[access "refs/meta/config"]
        read = group Admins
        push = group Admins
        forgeCommitter = group Admins
Mar 22, 2013
#1 sop@google.com
I'll try to take a look at this on the plane tomorrow.
Status: Accepted
Owner: sop@google.com
Mar 23, 2013
#2 sop@google.com
https://gerrit-review.googlesource.com/43883
Status: ChangeUnderReview
Mar 25, 2013
#4 sop@google.com
(No comment was entered for this change.)
Status: Submitted
Labels: FixedIn-2.6
Sign in to add a comment

Powered by Google Project Hosting