Git user accounts issue/changes?

[Alex Vakulenko]

Today my repo upload failed with the following error message:

remote: ERROR:  In commit 67489400c82c7a926fcdca1ad51590c1891dd0e7

remote: ERROR:  committer email address avaku...@chromium.org

remote: ERROR:  does not match your user account.

remote: ERROR:

remote: ERROR:  The following addresses are currently registered:

remote: ERROR:    avaku...@google.com

remote: ERROR:

remote: ERROR:  To register an email address, please visit:

remote: ERROR:  https://chromium-review.googlesource.com/#/settings/contact

So I started looking around but couldn't figure out why it is trying to use my google.com account instead of the chromium.org as set in git config. So, I decided to go to http://www.chromium.org/chromium-os/developer-guide/gerrit-guide and regenerate the passwords for both of my accounts. When clicking https://chromium-review.googlesource.com/new-password and https://chrome-internal-review.googlesource.com/new-password I noticed that the password generation page looks completely different. It used to give two lines per account which I needed to save to my ~/.netrc. Now it is talking about ~/.gitcookies and some weird bash commands.

Anyway, setting those the new way didn't work for me because it only set the password for chromium.googlesource.com and chrome-internal.googlesource.com but not the chromium-review. and chrome-internal-review. domains.

Anyway, I had to manually edit the ~/.gitcookies to add those records and now I can upload to Gerrit again.

The question is: is something going on that we should be aware of?

[Vadim Shtayura]

Gerrit recently changed the way passwords are provided from .netrc to cookiefile to workaround a bug in older versions of libcurl: netrc password larger than some limit gets truncated (and Google auth service started to generate tokens that trigger that bug). Any existing .netrc files should continue too function.

To get a proper .gitcookie file to work with both 'chromium' and 'chrome-internal' hosts you have two options:

1. Manually add host-specific lines to .gitcookie file, as you did (with @chromium.org password for 'chromium' site and @google.com one for 'chrome-internal').

2. Request to link @chromium.org & @google.com accounts on Gerrit and setup "all of googlesource.com" cookie file using either of @chromium.org or @google.com. This option assumes you do not use any other Gerrit hosts.

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

[Alex Vakulenko]

Well, a PSA on this would have been useful. Also, the old password generator gave tokens for both chromium and chromium-review (and chrome-internal and chrome-internal-review) domains, while the new one only has chromium and chrome-internal. The -review ones disappeared with this change, so people now need to add these to their ~/.gitcookies manually after the fact...

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-d...@chromium.org.

[Mike Frysinger]

i think we still need a PSA and updated documentation.  there is no mention of gitcookie in dev.chromium.org, only netrc.

plus i think our chromite tooling only supports netrc.

-mike

[Alex Vakulenko]

Yes, I just recreated my chroot and ~/.gitcookies is lost inside the chroot, but ~/.netrc has been ported from the host successfully... And yes, my main concern with this that I tried to follow the documentation pages and was struck with disparity of what dev.chromium.org was telling and what I was observing, so I wasn't sure if I was doing the right thing in the first place...

[Mike Frysinger]

someone reported the issue to this list a day or two ago.  he says he worked around by copying the password presented on the page to his .netrc.

e.g. this form:

.googlesource.com,TRUE,/,TRUE,2147483647,o,git-vapier.google.com=1/lkjam32008adsfmKLDSJnasdkjf1

copy & paste the bold portion to your .netrc:

machine chrome-internal-review.googlesource.com login git-vapier.google.com password 1/lkjam32008adsfmKLDSJnasdkjf1

and it should work

-mike

[Alex Vakulenko]

That's what I ended up doing too.

[Armin Lavaee]

Hi

i did this but still get the error. is there any other way to solve this funny problem that thanks to google we have for now??!!