when working on testing like the windows 8 ix maschines - i run into trouble when testing like cbook-1119:mozilla-central cbook$ hg push -f ssh://hg.mozilla.org/projects/ash pushing to ssh://hg.mozilla.org/projects/ash searching for changes remote: adding changesets remote: adding manifests remote: adding file changes remote: transaction abort! remote: rollback completed remote: abort: Permission denied: /repo/hg/mozilla/projects/ash/.hg/store/data/browser/modules/webrtc_u_i.jsm.i abort: unexpected response: empty string i guess i currently have level 2 commit access, does this error mean i need level 3 access ?
http://hg.mozilla.org/repo-group?repo=projects/ash says level_2, so that shouldn't be the problem...
Assignee: mozillamarcia.knous → server-ops
Component: Repository Account Requests → Server Operations
QA Contact: shyam
Your hg bit isn't stale. Looks like your SVN bit was (and fixed), but that shouldn't be relevant to this.
still failing :( bundling: xulrunner/examples/simple/components/Makefile.in 944/1090 files (86.61%) remote: adding changesets remote: adding manifests remote: adding file changes remote: transaction abort! remote: rollback completed remote: abort: Permission denied: /repo/hg/mozilla/projects/ash/.hg/store/data/browser/modules/webrtc_u_i.jsm.i abort: unexpected response: empty string
hm could it be that the checkin permissions were isolated to partner-stuff like https://hg.mozilla.org/build/partner-repacks/
Any progress here? Tomcat: are there any repos you can commit to? (your own user repos, shared build repos, etc.)
Your access looks good in LDAP. Punting to Developer Services to check.
Assignee: server-ops → server-ops-devservices
Component: Server Operations → Server Operations: Developer Services
Some of the files in the ash repository were inexplicably owned by scm_level_3. I've corrected the permissions and you should be able to push. Please let me know if you encounter any more issues.
Assignee: server-ops-devservices → bkero
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
thanks, so far its fixed, thanks ben!
Status: RESOLVED → VERIFIED
Component: Server Operations: Developer Services → General
Product: mozilla.org → Developer Services
You need to log in before you can comment on or make changes to this bug.