Re: Migration to subversion

2007-01-02 Thread Ross Golder
Clytie Siddall wrote: BTW, Ross, since we all need to checkout new working copies, do you want us to space it out in some way, or is a combined mad rush on the SVN server OK? It's a fairly capable server - I can't see a mad rush being a problem. The load on the server can be seen here:

Migration to subversion

2007-01-01 Thread Pema Geyleg
Hi all, I was closely following the migration of gnome from cvs to subversion. Let me congratulate for the successful migration first However I still havent figured out how we would be able to upgrade our translation for the gnome. We had CVS commit access for the translation work and now

Re: Migration to subversion

2007-01-01 Thread Žygimantas Beručka
Pr, 2007 01 01 18:16 +0600, Pema Geyleg rašė: However I still havent figured out how we would be able to upgrade our translation for the gnome. We had CVS commit access for the translation work and now am not sure whether we can commit our updates on svn with the same account or not. Yes

Re: Migration to subversion

2007-01-01 Thread Raphael Higino
On 1/1/07, Pema Geyleg [EMAIL PROTECTED] wrote: We had CVS commit access for the translation work and now am not sure whether we can commit our updates on svn with the same account or not. Just to confirm, I guess our mail aliases have also changed to [EMAIL PROTECTED], right? -- Raphael

Re: Migration to subversion

2007-01-01 Thread Priit Laes
Ühel kenal päeval, E, 2007-01-01 kell 13:13, kirjutas Raphael Higino: On 1/1/07, Pema Geyleg [EMAIL PROTECTED] wrote: We had CVS commit access for the translation work and now am not sure whether we can commit our updates on svn with the same account or not. Just to confirm, I guess our

Re: Migration to subversion

2007-01-01 Thread Matic Žgur
Hello, I keep getting these warnings when I check out from GNOME svn repository: svn: warning: cannot set LC_CTYPE locale svn: warning: environment variable LANG is sl_SI.UTF-8 svn: warning: please check that your locale name is correct These warnings appear only when I use developer checkout

Re: Migration to subversion

2007-01-01 Thread Danilo Šegan
Hi Pema, Yesterday at 13:16, Pema Geyleg wrote: Is there a document on what needs to be done from our side? I also saw the branch for gnome 2.18 and we would be updating to it after committing a last updates on gnome 2.14. Yes, you can still use your old account. To checkout a module from

SVN email aliases (was Re: Migration to subversion)

2007-01-01 Thread Danilo Šegan
Yesterday at 16:13, Raphael Higino wrote: Just to confirm, I guess our mail aliases have also changed to [EMAIL PROTECTED], right? A question for gnome-infrastructure. Guys? Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org

Re: Migration to subversion

2007-01-01 Thread Matic Žgur
Dne 01.01.2007 (pon) ob 18:15 +0100 je Matic Žgur zapisal(a): Hello, I keep getting these warnings when I check out from GNOME svn repository: svn: warning: cannot set LC_CTYPE locale svn: warning: environment variable LANG is sl_SI.UTF-8 svn: warning: please check that your locale name

Re: SVN email aliases (was Re: Migration to subversion)

2007-01-01 Thread Olav Vitters
On Tue, Jan 02, 2007 at 12:36:48AM +0100, Danilo Šegan wrote: Yesterday at 16:13, Raphael Higino wrote: Just to confirm, I guess our mail aliases have also changed to [EMAIL PROTECTED], right? A question for gnome-infrastructure. Guys? [EMAIL PROTECTED] works (and [EMAIL PROTECTED]

Re: Migration to subversion

2007-01-01 Thread Wouter Bolsterlee
2007-01-02 klockan 00:46 skrev Matic Žgur: I still haven't managed to fix this problem. It is not a serious one but it is quite an annoying one because I have to type ssh passphrase three times before it starts checking out. So if anyone knew what to do, I'd be very grateful. Use ssh-agent

Re: Migration to subversion

2007-01-01 Thread Clytie Siddall
On 02/01/2007, at 10:25 AM, Wouter Bolsterlee wrote: Use ssh-agent (you're probably running it already, since most distros include it by default in your XSession) and add your SSH key to it by using ssh-add. Then type your passphrase. Subsequent ssh invocations will not ask you for a