Closed
Bug 685145
Opened 13 years ago
Closed 13 years ago
Re-enable the calbld account
Categories
(Infrastructure & Operations Graveyard :: Account Requests, task)
Infrastructure & Operations Graveyard
Account Requests
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: standard8, Assigned: jlaz)
References
Details
calbld hasn't been used for a while because we haven't been doing releases of Lightning in an automated fashion. We're now getting started on these again, so please can that account be re-enabled.
Reporter | ||
Comment 1•13 years ago
|
||
To clarify, this is for Mercurial access. Can we get this done today please? we really need it in order to get Lightning releases running asap.
Severity: major → critical
Assignee | ||
Updated•13 years ago
|
Assignee: desktop-support → jlaz
Assignee | ||
Comment 2•13 years ago
|
||
Re-enabled HG bit, should be good
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 3•13 years ago
|
||
Unfortunately that doesn't seem to have fixed it. I'm still getting the same message: remote: Your mercurial account has been disabled due to inactivity. remote: Please file a bug at https://bugzilla.mozilla.org (or http://tinyurl.com/2aveg9k) to re-activate your account. abort: no suitable response from remote hg!
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 4•13 years ago
|
||
Try to commit once more. There is a 24-hour period where the bit becomes disabled if there is no activity (only happens when trying to re-enable an dormant account)
Comment 5•13 years ago
|
||
Tested as calbld with comm-central, see http://hg.mozilla.org/comm-central/rev/d6f1d7563de5
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → Infrastructure & Operations
Updated•9 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•