Closed
Bug 1473965
Opened 7 years ago
Closed 7 years ago
Change email to boris.chiou@gmail.com and restore Mercurial access
Categories
(Infrastructure & Operations :: MOC: Service Requests, task)
Infrastructure & Operations
MOC: Service Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: boris, Assigned: Usul)
Details
While calling "ssh hg.mozilla.org", I got the following messages:
A SSH connection has been established, your account (bchiou@mozilla.com)
was found in LDAP, and your account has been configured for Mercurial
access.
However, Mercurial access is currently disabled on your account.
This commonly occurs due to account inactivity (you need to SSH
into hg.mozilla.org every few months to keep your account active).
To restore Mercurial access, please file a MOC Service Request
bug (http://tinyurl.com/njcfhma) and request hg access be restored
for bchiou@mozilla.com.
Connection to hg.mozilla.org closed.
Could you please restore it? Thank you.
| Reporter | ||
Updated•7 years ago
|
Summary: Restore Mercurial access for bchiou@mozilla.com → Change email to boris.chiou@gmail.com and restore Mercurial access
| Reporter | ||
Comment 1•7 years ago
|
||
I have a LDAP account, but I would like to use boris.chiou@gmail.com to push try and inbound (Level 3) access. My level 3 access had been verified by Bug 1257596.
Comment 2•7 years ago
|
||
Ludo, what's the best way to go about this? Would be good to know for future requests.
Assignee: nobody → ludovic
Status: NEW → ASSIGNED
| Assignee | ||
Comment 3•7 years ago
|
||
So HG and level3 were gone from the moco account. Re-added them.
(In reply to Boris Chiou [:boris] from comment #1)
> I have a LDAP account, but I would like to use boris.chiou@gmail.com to push
> try and inbound (Level 3) access. My level 3 access had been verified by Bug
> 1257596.
I'll create the new contributor account.
Account created. Email with credentials sent.
Added level3 and HG. Can you add your key when you change the password Boris , thanks.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•