Closed Bug 1182230 Opened 9 years ago Closed 9 years ago

Please add me to the SVN repo [/mozillamessaging.com/sites/autoconfig.mozillamessaging.com/trunk]

Categories

(Developer Services :: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: asuth, Assigned: fubar)

References

Details

Greater context: bug 1169687 and https://mail.mozilla.org/pipermail/tb-planning/2013-August/002884.html (I was a bit delayed on the follow-through there...)

We are in the process of formalizing the Thunderbird autoconfiguration/ISPDB database as a formal (sub)module (and wanting to move it off of subversion).  I will be proposing the (sub)module in the next few days as I hear back from the existing peer list whether they want to be on there, but in the interim I would like to be able to land reviewed patches so I can start to clear out the backlog and we don't get stalled by debates about whether the (sub)module should live under services (sub)modules or hg/git migration.

:BenB is the de facto owner of the ISPDB and will be the formal owner, and per discussion with him, I am joining as a peer.  I've cc'ed for his awareness/etc.  :rkent is the chair of the Thunderbird Council who was involved in bug 1169867 who I've also cc'ed.  I'm also cc'ing :mkmelin, the owner of the Thunderbird module, which I think is the module we want to root the ISPDB under.

Note that my LDAP auth creds are under bugmail@asutherland.org but I'm also asuth@mozilla.com.
(In reply to Andrew Sutherland [:asuth] from comment #0)
>
> Note that my LDAP auth creds are under bugmail@asutherland.org but I'm also
> asuth@mozilla.com.

Added both. Puppet should have it updated within an hour.
Assignee: nobody → klibby
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
This isn't working for me no matter how I try.  I've never had svn access before (although I had CVS and still should have hg access on bugmail@asutherland.org unless I haven't been pushing enough), could that impact things?  (While trying to understand the error messages, I found bug 1135512 where that seemed to be an issue.)  My apologies if it turns out I'm doing something dumb; I've tried to consult the appropriate resources.

The most-working configuration seems to be my asuth@mozilla.com as "asuth". (I verified at login.mozilla.com that it has my key fingerprint and it says my SSH username is "asuth".)  It does not complain about me not having an account, but doesn't like the repo:
$ svn co svn+ssh://asuth@svn.mozilla.org/mozillamessaging.com/sites/autoconfig.mozillamessaging.com/trunk autoconfig-db
svn: E210002: Unable to connect to a repository at URL 'svn+ssh://asuth@svn.mozilla.org/mozillamessaging.com/sites/autoconfig.mozillamessaging.com/trunk'
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


If I do that but scoping to mozilla.com, it complains about the account (and the home directory?):
$ svn co svn+ssh://asuth@mozilla.com@svn.mozilla.org/mozillamessaging.com/sites/autoconfig.mozillamessaging.com/trunk autoconfig-db
Could not chdir to home directory : No such file or directory
You do not have a valid subversion account here!
svn: E210002: Unable to connect to a repository at URL 'svn+ssh://asuth@mozilla.com@svn.mozilla.org/mozillamessaging.com/sites/autoconfig.mozillamessaging.com/trunk'
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


And my bugmail identity fails without a home directory error, but still with a user error.  And I do have a "User" line of "bugmail@asutherland.org" in my ~/.ssh/config that works for hg, so I think that's right:
$ svn co svn+ssh://bugmail@asutherland.org@svn.mozilla.org/mozillamessaging.com/sites/autoconfig.mozillamessaging.com/trunk autoconfig-dbYou do not have a valid subversion account here!
svn: E210002: Unable to connect to a repository at URL 'svn+ssh://bugmail@asutherland.org@svn.mozilla.org/mozillamessaging.com/sites/autoconfig.mozillamessaging.com/trunk'
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


Thanks!
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 1185521
bah, I didn't think to verify that you had general SVN access enabled. requested in 1185521!
andrew, give it another whirl?
Flags: needinfo?(bugmail)
They both work, thank you!

(For my own future reference, I do need to use "asuth@mozilla.com" for the MoCo creds.)

And we will try and get this migrated onto hg/git etc. in the medium (or better) term, so we can all be free of svn!
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Flags: needinfo?(bugmail)
Resolution: --- → FIXED
So, although I can get a fresh checkout right now from both accounts, neither of them are allowed to commit:

$ svn commit -m "Bug 528484: Add yahoo.se to yahoo.com aliases. r=asuth on change proposed by andreasn"
Sending        yahoo.com
Transmitting file data .svn: E000013: Commit failed (details follow):
svn: E000013: Can't open file '/repo/svn/mozilla/db/txn-current-lock': Permission denied

From bug 1047524 it seems like this error could be an LDAP privileges thing, but bug 951059 makes it seem like it could just be an infra thing.  So I tried doing this several times spread over several minutes, and it always dislikes me.  I'll try again much later, but I'm tentatively going to assume I need more help.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Flags: needinfo?(klibby)
I made an assumption about what bits get flipped when enabling a SVN account that was incorrect. /sadtrombone  Reopened the MOC bug to have correct bit enabled.
Flags: needinfo?(klibby)
I tested both accounts and am able to commit successfully.  Thanks again!
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.