Closed
Bug 374974
Opened 17 years ago
Closed 17 years ago
CVS Account Request - Mark Charlebois <mcharleb@qualcomm.com >
Categories
(mozilla.org :: Repository Account Requests, task)
mozilla.org
Repository Account Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mcharleb, Assigned: oremj)
Details
Attachments
(1 file, 1 obsolete file)
610 bytes,
text/plain
|
Details |
The Penelope project needs at least one developer with CVS access to update the mozilla/penelope and extensions/penelope trees. Curretly we have to burden Scott or David with all of our requests for Penelope specific changes. I have submitted the majority of the Penelope extension code that is currently checked into the mozilla trunk.
Comment 1•17 years ago
|
||
Marcia, penelope now has its own top level directory in the repository. mozilla\penelope It's not part of the default seamonkey module and is not part of the build for Firefox, Thunderbird, etc. Can we grant Mark CVS access with the understanding that it's for making changes limited to mozilla\penelope without going through the normal mozilla CVS access policy? FYI, I've got a note to make sure Penelope gets listed as a module with the appropriate listed peers once Stuart's done updating the module owners page.
Comment 2•17 years ago
|
||
This sounds ok to me. If mark can get the CVS form to me (www.mozilla.org/hacking/form.html) as well as attach a SSH key to the bug, we can get this rolling. (In reply to comment #1) > Marcia, penelope now has its own top level directory in the repository. > > mozilla\penelope > > It's not part of the default seamonkey module and is not part of the build for > Firefox, Thunderbird, etc. > > Can we grant Mark CVS access with the understanding that it's for making > changes limited to mozilla\penelope without going through the normal mozilla > CVS access policy? > > FYI, I've got a note to make sure Penelope gets listed as a module with the > appropriate listed peers once Stuart's done updating the module owners page. >
Status: NEW → ASSIGNED
Reporter | ||
Comment 3•17 years ago
|
||
Updated•17 years ago
|
OS: Linux → All
Hardware: PC → All
Summary: Create CVS account for mozilla/Penelope development → CVS Account Request - Mark Charlebois <mcharleb@qualcomm.com>
Reporter | ||
Comment 4•17 years ago
|
||
I have faxed the CVS Contributor's form
Comment 5•17 years ago
|
||
account created for access in mozilla\penelope directory only. Over to server-ops for SSH key, I still need to follow up re: the form but I am okay with moving this forward.
Assignee: marcia → server-ops
Status: ASSIGNED → NEW
Assignee | ||
Updated•17 years ago
|
Assignee: server-ops → oremj
Assignee | ||
Comment 6•17 years ago
|
||
Your CVS account has been created. Your CVSROOT should be: mcharleb%qualcomm.com@cvs.mozilla.org:/cvsroot Don't forget to set your CVS_RSH environment variable to 'ssh'. If you have any problems connecting, let me know.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 7•17 years ago
|
||
(In reply to comment #6) > Your CVS account has been created. Your CVSROOT should be: > > mcharleb%qualcomm.com@cvs.mozilla.org:/cvsroot > > Don't forget to set your CVS_RSH environment variable to 'ssh'. > > If you have any problems connecting, let me know. > I believe I attached the wrong part of the keypair in my previous attachment. I discovered this when I tried to use CVS with SSH and it was not working. I have generated a new key and will attach the new pub part. The error I was getting was: % cvs co mozilla/client.mk Permission denied (publickey,gssapi-with-mic). cvs [checkout aborted]: end of file from server (consult above messages if any)
Reporter | ||
Comment 8•17 years ago
|
||
I sent the wrong part of the keypair last time. I regenerated new keys and send the pub portion in this attachment.
Attachment #259364 -
Attachment is obsolete: true
Comment 9•17 years ago
|
||
re-opening the bug so we can get Mark's SSH key fixed.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 10•17 years ago
|
||
Oops, suprised I didn't catch that. You should be set now.
Status: REOPENED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•