Closed
Bug 976214
Opened 11 years ago
Closed 11 years ago
Can you please re-activate my svn account?
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Assigned: afernandez)
Details
Please :)
Updated•11 years ago
|
Assignee: mozillamarcia.knous → server-ops
Component: Repository Account Requests → Server Operations: Account Requests
QA Contact: tfairfield
| Assignee | ||
Comment 1•11 years ago
|
||
Done, like captain planet once said; "The Power is YOURS!"
Assignee: server-ops → afernandez
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 2•11 years ago
|
||
Is there a chance that we could bump the expiry from 6 months to 2 years?
I don't know how many new hires Release Engineering will have in the next 6 months (since I add their blog posts to the Releng planet).
Updated•11 years ago
|
Component: Server Operations: Account Requests → Server Operations
QA Contact: tfairfield → shyam
| Assignee | ||
Comment 3•11 years ago
|
||
We don't have the "right" to change the expiration limit.
gerv can you comment?
Assignee: afernandez → server-ops
Flags: needinfo?(gerv)
| Assignee | ||
Updated•11 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 4•11 years ago
|
||
This isn't within my power. But anyone who has had a privilege in the past, unless it gets actively revoked, should be able to reactivate their account just by asking.
If you only check in less than every 6 months, consider filing a bug, attaching a patch and asking someone else to check in for you :-)
Gerv
Flags: needinfo?(gerv)
Updated•11 years ago
|
Assignee: server-ops → afernandez
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 5•11 years ago
|
||
My rw access does not work (see bug 971159).
Can someone please help me?
Sending releng/config.ini
Transmitting file data .svn: E220004: Commit failed (details follow):
svn: E220004: Access denied
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 6•11 years ago
|
||
messages:Feb 26 10:09:16 svn1 sshd[24385]: Failed publickey for armenzg@mozilla.com from 10.8.74.212 port 17053 ssh2
messages:Feb 26 10:09:16 svn1 sshd[24385]: Accepted publickey for armenzg@mozilla.com from 10.8.74.212 port 17053 ssh2
pash.log:ERROR:root:Failed to update LDAP attributes for armenzg@mozilla.com
pash.log:ERROR:root:Failed to update LDAP attributes for armenzg@mozilla.com
pash.log:ERROR:root:Failed to update LDAP attributes for armenzg@mozilla.com
pash.log:ERROR:root:Failed to update LDAP attributes for armenzg@mozilla.com
pash.log:ERROR:root:Failed to update LDAP attributes for armenzg@mozilla.com
pash.log:ERROR:root:Failed to update LDAP attributes for armenzg@mozilla.com
pash.log:ERROR:root:Failed to update LDAP attributes for armenzg@mozilla.com
pash.log:ERROR:root:Failed to update LDAP attributes for armenzg@mozilla.com
pash.log:ERROR:root:Failed to update LDAP attributes for armenzg@mozilla.com
pash.log:ERROR:root:Failed to update LDAP attributes for armenzg@mozilla.com
pash.log:ERROR:root:Failed to update LDAP attributes for armenzg@mozilla.com
pash.log:ERROR:root:Failed to update LDAP attributes for armenzg@mozilla.com
Comment 7•11 years ago
|
||
Feb 26 06:43:08 svn1 sshd[7204]: Failed publickey for armenzg@mozilla.com from 10.8.74.212 port 33937 ssh2
Feb 26 06:43:08 svn1 sshd[7204]: [LDAP] Found matching DSA key: 26:30:e8:f7:ad:14:3c:34:0e:fd:a5:b4:fe:0e:fb:04
Feb 26 06:43:08 svn1 sshd[7204]: [LDAP] Found matching DSA key: 26:30:e8:f7:ad:14:3c:34:0e:fd:a5:b4:fe:0e:fb:04
Feb 26 06:43:08 svn1 sshd[7204]: Accepted publickey for armenzg@mozilla.com from 10.8.74.212 port 33937 ssh2
Are you using the proper ssh key ?
Comment 8•11 years ago
|
||
I looked at this but couldn't find any problems. I did s/armengz/armenzg/ in /repo/svn/mozilla/conf/authz, so that's a start.
Here's from a pastebin of Armen trying to commit:
armenzg-thinkpad branches $ svn commit -m "Adding Releng's feed"
Sending releng/config.ini
Transmitting file data .svn: E220004: Commit failed (details follow):
svn: E220004: Access denied
Comment 9•11 years ago
|
||
digi, could you look at this? I know you have experience with the svn setup
Comment 10•11 years ago
|
||
:armenzg,
Could you try using https instead of svn+ssh? I'm assuming you're
trying to commit to:
https://svn.mozilla.org/projects/planet/branches/releng
| Reporter | ||
Comment 11•11 years ago
|
||
After clobbering and starting again:
armenzg-thinkpad repos $ svn co https://svn.mozilla.org/projects/planet .
armenzg-thinkpad repos $ cd planet
armenzg-thinkpad planet $ svn up
Updating '.':
At revision 125073.
armenzg-thinkpad planet $ patch -p0 < ~/moz/patches/releng.diff
armenzg-thinkpad planet $ svn commit -m "Adding Releng's feed"
Authentication realm: <https://svn.mozilla.org:443> Mozilla LDAP
Password for 'armenzg':
Authentication realm: <https://svn.mozilla.org:443> Mozilla LDAP
Username: armenzg@mozilla.com
Password for 'armenzg@mozilla.com':
Sending branches/releng/config.ini
Transmitting file data .svn: E195023: Commit failed (details follow):
svn: E195023: Changing file '/home/armenzg/repos/planet/branches/releng/config.ini' is forbidden by the server
svn: E175013: Access to '/!svn/txr/125073-2ozq/projects/planet/branches/releng/config.ini' forbidden
Comment 12•11 years ago
|
||
We resolved this on IRC. The authz file contained a typo'd username and the path had a breaking trailing slash.
Updated•11 years ago
|
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•10 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
•