Hello all, We are working on synchronization of tizen repositories to version API 2.2.
All bugs are labeled "upgrade_to_2.2" on Public Jira. we are facing to several different gerrit issues when we are trying to commit the merge content. Does anybody get the below Gerrit issues? - First issue seen : Merge commit without changeID. exemple for wrt package (platform/framework/web/wrt) : *---------------------------------------------------------------------------------------------------------------------------------------------------[tizen 6960494] Merge remote-tracking branch 'sam/tizen_2.2' into tizen~/tmp/wrt(tizen)$ git push origin HEAD:refs/for/tizenCounting objects: 439, done.Delta compression using up to 8 threads.Compressing objects: 100% (239/239), done.Writing objects: 100% (311/311), 140.48 KiB, done.Total 311 (delta 235), reused 121 (delta 68)remote: Resolving deltas: 100% (235/235)remote: remote: Processing changes: refs: 1, done remote: ERROR: missing Change-Id in commit message footerremote: Suggestion for commit message:remote: Initial empty repositoryremote: remote: Change-Id: I3f8c4f892d1679dccaa9a1b31f357fc39f3f3f3fremote: remote: Hint: To automatically insert Change-Id, install the hook:remote: scp -p -P 29418 [email protected]:hooks/commit-msg .git/hooks/remote: remote: To review.tizen.org:platform/framework/web/wrt ! [remote rejected] HEAD -> refs/for/tizen (missing Change-Id in commit message footer)error: failed to push some refs to 'review.tizen.org:platform/framework/web/wrt'---------------------------------------------------------------------------------------------------------------------------------------------------* According to the log, gerrit rejects the merge because of a commit without change-id. This commit is the first of the branch that we re trying to merge.(branch tizen2.2 of repository framework/web/wrt), we do not have permission on this last repository (framework/web/wrt) Is there a way to bypass this ? - second issue seen : committer is not the same person that do the merge. example for vconf component : *---------------------------------------------------------------------------------------------------------------------------------------------------[tizen 68fcdeb] Merge remote-tracking branch 'sam/tizen_2.2' into tizen ~/TIZEN/git_std/vconf(tizen)$ git push origin HEAD:refs/for/tizenCounting objects: 40, done.Delta compression using up to 8 threads.Compressing objects: 100% (23/23), done.Writing objects: 100% (23/23), 3.53 KiB, done. Total 23 (delta 20), reused 0 (delta 0)remote: Resolving deltas: 100% (20/20)remote: remote: Processing changes: refs: 1, done remote: remote: ERROR: In commit eef40364677d595129d249ebd2f2ad* *497ff0f142 remote: ERROR: committer email address [email protected] <[email protected]>remote: ERROR: does not match your user account.remote: ERROR:remote: ERROR: The following addresses are currently registered: remote: ERROR: [email protected] <[email protected]>remote: ERROR: [email protected] <[email protected]>remote: ERROR: remote: ERROR: To register an email address, please visit:remote: ERROR: https://review.tizen.org/gerrit/#/settings/contact <https://review.tizen.org/gerrit/#/settings/contact>remote: remote: To review.tizen.org:platform/* *core/appfw/vconf ! [remote rejected] HEAD -> refs/for/tizen (invalid committer)error: failed to push some refs to 'review.tizen.org:platform/* *core/appfw/vconf'* *---------------------------------------------------------------------------------------------------------------------------------------------------* Same question is there way to bypass this check? Is there a way to do such synchronization through Gerrit? Thanks in advance for your help Baptiste -- Baptiste DURAND Intel OTC - Vannes/FR
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
