Closed Bug 685145 Opened 13 years ago Closed 13 years ago

Re-enable the calbld account

Categories

(Infrastructure & Operations Graveyard :: Account Requests, task)

task
Not set
critical

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.
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: desktop-support → jlaz
Re-enabled HG bit, should be good
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
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 → ---
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)
Tested as calbld with comm-central, see http://hg.mozilla.org/comm-central/rev/d6f1d7563de5
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Yep, working nicely now, thanks.
Status: RESOLVED → VERIFIED
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.