Created attachment 8661966 [details] Public key I can no longer check in to hg.mozilla.org, presumably because my firstname.lastname@example.org account and LDAP credentials are no longer active. Please reactivate hg access for email@example.com.
That is correct, do you have the commit access bug(s) numbers? I'll need to reference them for setting up the right bits.
Bug 75579 was my original CVS access.
Not seeing an account for firstname.lastname@example.org.
The account was most recently for email@example.com; before that it was for firstname.lastname@example.org (and before that for email@example.com).
Alright, new account created, key added, credentials were sent to email. Let me know if you have the required access.
Assignee: nobody → rchilds
Status: NEW → ASSIGNED
I can now authenticate with the new account, but I still can't push: $ hg push -f try pushing to ssh://firstname.lastname@example.org/try/ searching for changes remote: abort: could not lock repository /repo/hg/mozilla/try/: Permission denied abort: unexpected response: empty string
Simon, Try should now be enabled. Give this about 30 minutes to propagate.
Thanks, try is now fine, but mozilla-inbound still is not. Should I have explicitly requested access for mozilla-inbound and mozilla-central? I thought that was obvious :-S
Simon, My apologizes, I don't see either of those bits, nor do I see any credentials in your email@example.com account to compare to. NI'ing Marcia to see what those are comparable to, since I think mozilla-inbound and mozilla-central are legacy.
(In reply to Ryan C [:ryanc] from comment #9) > Simon, > > My apologizes, I don't see either of those bits, nor do I see any > credentials in your firstname.lastname@example.org account to compare to. > > NI'ing Marcia to see what those are comparable to, since I think > mozilla-inbound and mozilla-central are legacy. CVS access meant level3 access , if try works and others don't then you just gave him level1. Granted access level3 to Simon. commit away.
Alright, Assuming that worked. Please reopen if otherwise.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.