l10n CVS account for Simon Paquet

RESOLVED FIXED

Status

RESOLVED FIXED
11 years ago
10 years ago

People

(Reporter: sipaq, Assigned: justdave)

Tracking

Details

(Reporter)

Description

11 years ago
As the l10n head for the Calendar Project it would be good to get access to the l10n repository as well, as I get lots of requests (which I have to deny right now) to help with committing new locales or updating locales for the Calendar Project products Lightning and Sunbird.

I currently have a cvs, cvs-www and an ftp-stage account all pointing to the same key. It would be great if my l10n account could use the same key as well.

Comment 1

11 years ago
Getting bugmail for this once, is good enough, un-CC axel@pike.org.

The actual account creation is fine with me, of course.
You actually need to set the proper assignee and QA contact, or we don't see the bugs. :)
Assignee: registration → marcia
QA Contact: registration → justdave
As Axel said this is ok, just sending directly to IT. IT will just add the l10nsrc group to your CVS account.
Assignee: marcia → server-ops
Assignee: server-ops → justdave
Your account has been granted access to the l10n repo
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
(Reporter)

Comment 5

10 years ago
Reopening.

Dave, when trying to change something in the repository, I get an error message that I need write access to the repository.


This is my Windows batch file that I used for logging into the cvs server (in case that information helps):

|@echo off
|set MOZ_TOOLS=c:\moztools
|set CVSROOT=:ext:bugzilla%%babylonsounds.com@cvs.mozilla.org:/l10n
|set HOME=c:\mozilla
|set PATH=%PATH%;%MOZ_TOOLS%\bin;C:\cygwin\bin;
|set CVS_RSH=ssh.exe
|
|cd mozilla\l10n
|
|for /f "tokens=1,2,3* delims=; " %%a in ('ssh-agent -c') do if "%%a"=="setenv" set %%b=%%c
|set HOME=C:\cygwin\home
|ssh-add C:\cygwin\id_dsa2
|start /b /wait cmd.exe
|ssh-agent -k
|exit
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Hate to be pedantic, but please open a new bug for this.  Your account did get created - a long time ago, at that - which is what this bug was asking for.
Status: REOPENED → RESOLVED
Last Resolved: 11 years ago10 years ago
Resolution: --- → FIXED
Just double-checked your account anyway, and everything is set up how it's supposed to be.  This must be a technical issue on your end.  Ask around on #developers would be your best bet as I know exceedingly little about Windows.
You need to log in before you can comment on or make changes to this bug.