Closed Bug 1142226 Opened 7 years ago Closed 7 years ago

Commit Access (Level l10n) for Stoyan Dimitrov

Categories

(Infrastructure & Operations :: MOC: Service Requests, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: marcia, Assigned: rwatson)

References

Details

+++ This bug was initially created as a clone of Bug #1141043 +++

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0
Build ID: 20150305191659

Please create an Level 1-l10n account for this localizer. He will need LDAP/SVN.


Expected results:

I need commit access to continue maintaining Firefox Web parts for Bulgarian.
I will be using stoyan@gmx.com for login. Currently I don't have LDAP account.

I have read, and agree to abide by, the Commit Access Requirements.
Assignee: nobody → vhua
-LDAP account created, emailed password
-added RSA keys
-enabled cn=scm_l10n,ou=groups,dc=mozilla 

Let me know if user has any issues.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
$ svn checkout svn+ssh://svn.mozilla.org/projects/l10n-misc/trunk/firefox-ios/bg/ firefox-ios
Enter passphrase for key '/home/stoyan/keys/mozilla/id_rsa':
You do not have a valid subversion account here!
svn: E210002: Unable to connect to a repository at URL 'svn+ssh://svn.mozilla.org/projects/l10n-misc/trunk/firefox-ios/bg'
svn: E210002: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file.
svn: E210002: Network connection closed unexpectedly


It says 'You do not have a valid subversion account here!'.
I enabled the SVN bit.  Please try again, may take a few minutes to sync.
The checkout went ok, but can not commit.

$ svn commit -m "Partial Bulgarian translation to test the SVN account."
Enter passphrase for key '/cygdrive/d/keys/mozilla/id_rsa':
svn: E170001: Commit failed (details follow):
svn: E170001: Authorization failed
added cn=svn_mozilla,ou=groups,dc=mozilla

Please try now.
Still the same output. Am I doing something wrong?

$ svn commit -m "Partial Bulgarian translation to test the SVN account."
Enter passphrase for key '/cygdrive/d/keys/mozilla/id_rsa':
svn: E170001: Commit failed (details follow):
svn: E170001: Authorization failed
Hi,

I made a change. Please allow 15 minutes and try again and let me know.
Assignee: vhua → rwatson
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Hi, Ryan.
The output is the same.

> $ svn commit -m "Partial Bulgarian translation to test the SVN account."
> Enter passphrase for key '/cygdrive/d/keys/mozilla/id_rsa':
> svn: E170001: Commit failed (details follow):
> svn: E170001: Authorization failed

Although,
> $ ssh svn.mozilla.org -i /cygdrive/d/keys/mozilla/id_rsa
> Enter passphrase for key '/cygdrive/d/keys/mozilla/id_rsa':
> ( success [stripped, since I don't know how sensitive this info is] )
wierd. The permissions asked for have been granted for sure. Can you confirm that the level requested will allow you access to the place you need to commit to?
I am trying to access those two trees:
> svn+ssh://svn.mozilla.org/projects/mozilla.com/trunk/locales/bg/
> svn+ssh://svn.mozilla.org/projects/l10n-misc/trunk/firefox-ios/bg/

Reading similar bugs I am reaching to the conclusion than I was too specific needing level1-l10n access. Bug 1129901 and bug 1129918 doesn't mention access level (only "@localizers group on SVN"), but I am sure the resulting account has access to the first tree at least.
Probably the  access level is wrong. Frankly, I don't know how to test.
Yeah, I have no idea which levels have access to what parts of the tree. Can you find out from someone who currently has access? Perhaps the original bug? Once we find out and have approvals I can bump up the permissions?
Is Bug 1101580 comment 6 helpful?
I think i have this figured out. 

Can you test in 15 mins or so.. 

For other MOC people who are reading, we needed to add him to @localizers:
svn/files/svn/mozilla

Can you test and let me know.
I have the commit rights to the both trees now. Thank you.
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.