User-Agent: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:220.127.116.11) Gecko/20060516 SeaMonkey/1.0.2 Mnenhy/0.7.3.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:18.104.22.168) Gecko/20060516 SeaMonkey/1.0.2 Mnenhy/0.7.3.0 I'm in charge of toolkit translation for es-ES now, and actually I've got Thunderbird translation up to date, too. While Andrés García Aragoneses is on his way to get Firefox and will be available to commit all products L10N to CVS, we believe is good to have a backup for accessing to CVS. Currently, Andres is the only es-ES team member with access to CVS. Reproducible: Always
Created attachment 227811 [details] SSH public key Added my SSH public key. The CVS form was faxed yesterday at UTC 23:48. It will be in the mail today or (more probably) monday.
I am currently the unique es-ES localizer with CVS account, so I suppose I can vouch here to propose Ricardo as a peer.
Printed form has been put on the snail-mail today.
Will be on the lookout for the fax when the office reopens on 7-5. In the meantime I do need someone to vouch as well.
Beefing up the voucher of the locale owner, i.e., vouching.
fax form received - axel is this one ready to go?
yes, please. This should help fx2 l10n for spanish, so the sooner the better. Even if we filed it late.
over to server-ops for account creation.
Your CVS account has been created. Your CVSROOT should be: email@example.com:/l10n Don't forget to set your CVS_RSH environment variable to 'ssh'. If you have any problems connecting, let me know.
(In reply to comment #9) > Your CVS account has been created. Your CVSROOT should be: > > firstname.lastname@example.org:/l10n > > Don't forget to set your CVS_RSH environment variable to 'ssh'. > > If you have any problems connecting, let me know. > I keep getting this message: Permission denied (publickey,gssapi-with-mic). I've set CVS_RSH, I've replaced all of my CVS/Root entries so they use :ext:email@example.com:/l10n instead of :pserver:... and I've tried in a new, emtpy directory. One thing that could be related: my SSH pair uses my internal Linux login, which is not the same than firstname.lastname@example.org. Could that be the problem? If so, how could we solve it without filing a new bug? Maybe could I just generate a new pair with the right identity and add the public key here again? Sorry for annoying you.
(In reply to comment #10) > I keep getting this message: > > Permission denied (publickey,gssapi-with-mic). > Thanks to Axel, all this is working OK now (as you could assume, the fault was on my side). :-)