Re: Migration to subversion
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: http://sysadmin.gnome.org/mrtg/socket/load.html -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Migration to subversion
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 password anymore. If you want to automate some of the above, see my blog entries at [1] and [2] for more information. mvrgr, Wouter [1] http://uwstopia.nl/blog/2006/08/password-hell-gdm-ssh-gnome- keyring [2] http://uwstopia.nl/blog/2006/08/password-hell-part-ii For OSX users, as GUI frontends to ssh-add, ssh-agent and the usual CLI suspects, these can be handy: SSHAgent: http://www.phil.uu.nl/~xges/ssh/ SSHKeychain: http://www.sshkeychain.org/ SSH Tunnel Manager: http://projects.tynsoe.org/en/stm/download.php I run these in the background, and SSH checkouts etc., even those via a tunnel like OpenOffice.org, are a single command. 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? from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Migration to subversion
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 (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 password anymore. If you want to automate some of the above, see my blog entries at [1] and [2] for more information. mvrgr, Wouter [1] http://uwstopia.nl/blog/2006/08/password-hell-gdm-ssh-gnome-keyring [2] http://uwstopia.nl/blog/2006/08/password-hell-part-ii -- :wq mail [EMAIL PROTECTED] web http://uwstopia.nl no narcotics in my brain :: can make this go away -- porcupine tree signature.asc Description: Digital signature ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: SVN email aliases (was Re: Migration to subversion)
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] currently as well) -- Regards, Olav ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Migration to subversion
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 is correct > > These warnings appear only when I use developer checkout and not > when I anonymously check out a module. > > Does anyone knows what I can do to fix this? > > Thanks, > Matic Zgur Hi, 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. Cheers, Matic Zgur ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
SVN email aliases (was Re: Migration to subversion)
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 http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Migration to subversion
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 'HEAD' (now called 'trunk'), you'd now instead do: svn co svn+ssh://[EMAIL PROTECTED]/svn/MODULE/trunk DIRECTORY eg. svn co svn+ssh://[EMAIL PROTECTED]/svn/gtk+/trunk gtk+ To check it out from any other branch, you'd have to do: svn co svn+ssh://[EMAIL PROTECTED]/svn/MODULE/branches/BRANCH DIRECTORY eg. svn co svn+ssh://[EMAIL PROTECTED]/svn/gtk+/branches/gtk-2-10 gtk+.gtk-2-10 When you update your translation in DIRECTORY/po (just like before, either using file from progress.gnome.org or using intltool-update on your translation), and add a ChangeLog entry, you commit them using 'svn ci': svn ci -m 'Updated LANGUAGE translation.' I'll be adding svn-commit hooks to be able to update status pages almost-real-time (i.e. they will be regenerated as soon as you commit your translation). Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Migration to subversion
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 and not when I anonymously check out a module. Does anyone knows what I can do to fix this? Thanks, Matic Zgur ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Migration to subversion
Ü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 mail aliases have also changed to > [EMAIL PROTECTED], right? > Yes, at least worked for me. -- Priit Laes plaes.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Migration to subversion
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 Higino ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Migration to subversion
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 you can, I've committed some stuff already. For example: $ ssh-add $ svn co svn+ssh://[EMAIL PROTECTED]/svn/gimp/trunk gimp ...after your changes commit with $ svn ci Žygis ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Migration to subversion
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 am not sure whether we can commit our updates on svn with the same account or not. 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. Many Thanks Pema Geyleg DIT, Bhutan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n