Closed
Bug 389493
Opened 17 years ago
Closed 17 years ago
CVS checkout fails with "failed to create lock directory" error for toolkit/crashreporter/#cvs.lock
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: myk, Assigned: reed)
Details
A standard CVS checkout of the trunk is failing with the following error: cvs checkout: failed to create lock directory for `/cvsroot/mozilla/toolkit/crashreporter' (/cvsroot/mozilla/toolkit/crashreporter/#cvs.lock): Permission denied cvs checkout: failed to obtain dir lock in repository `/cvsroot/mozilla/toolkit/crashreporter' cvs [checkout aborted]: read lock failed - giving up shaver speculates it might have something to do with work that reed was doing on breakpad.
Reporter | ||
Comment 1•17 years ago
|
||
Raising this to the highest severity level, as it looks to be preventing all clients (including all tinderboxes) from cleanly updating their trees, leaving trees in a partially-updated state when the process fails.
Severity: critical → blocker
Assignee | ||
Updated•17 years ago
|
Assignee: server-ops → reed
Assignee | ||
Comment 2•17 years ago
|
||
So, for some reason, some of the directories that were copied as part of bug 371069 did not have g+w set so that the mozsrc group could write to them (they had g+s already, but not g+w). The original directories have the appropriate permissions, so I'm not sure why the copy failed to correctly set some of the permissions for some directories but not for all of them. I have chmod'd all the directories under toolkit/crashreporter/ g+w, so this should be fixed. CVS copying is all automated, so I find this quite weird. I will work with justdave to see why the script didn't do this correctly so that this doesn't happen again.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 3•17 years ago
|
||
Yup, this looks fixed now. Thanks Reed!
Status: RESOLVED → VERIFIED
Updated•9 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•