As discussed some time ago, Berlios will switch off the SVN service by the end of the year and thus we must move.
I proposed to our SVN experts to start the move on 2011-11-29. This means, Berlios will be switched to a read-only state and we will start copying the files with all the history and revisions to opensuse.org. This will probably take some days.
Do you have any concerns about the timing and the procedure? For openSUSE, we still have the possibility to finish the currect release notes and do other online updates, if needed. For SLE 11 SP2, we can prepare the RC2 release as planned.
ATM, I do not know how we can preserve the accounts or the account names. Stay tuned...
SVP ne m'écrivez plus merci
----- Original Message ----- From: "Karl Eichwalder" ke@suse.de To: opensuse-translation@opensuse.org Cc: swims@novell.com; pdillon@novell.com Sent: Thursday, November 17, 2011 9:54 AM Subject: [opensuse-translation] Moving SVN to opensuse.org
As discussed some time ago, Berlios will switch off the SVN service by the end of the year and thus we must move.
I proposed to our SVN experts to start the move on 2011-11-29. This means, Berlios will be switched to a read-only state and we will start copying the files with all the history and revisions to opensuse.org. This will probably take some days.
Do you have any concerns about the timing and the procedure? For openSUSE, we still have the possibility to finish the currect release notes and do other online updates, if needed. For SLE 11 SP2, we can prepare the RC2 release as planned.
ATM, I do not know how we can preserve the accounts or the account names. Stay tuned...
On Thursday, November 17, 2011 09:54:22 Karl Eichwalder wrote:
As discussed some time ago, Berlios will switch off the SVN service by the end of the year and thus we must move.
I proposed to our SVN experts to start the move on 2011-11-29. This means, Berlios will be switched to a read-only state and we will start copying the files with all the history and revisions to opensuse.org. This will probably take some days.
Do you have any concerns about the timing and the procedure? For openSUSE, we still have the possibility to finish the currect release notes and do other online updates, if needed. For SLE 11 SP2, we can prepare the RC2 release as planned.
ATM, I do not know how we can preserve the accounts or the account names. Stay tuned...
An alternative is switching to github.com. Besides git it supports svn - and also editing of files via the web.
Andreas
2011/11/17 Andreas Jaeger aj@suse.com:
On Thursday, November 17, 2011 09:54:22 Karl Eichwalder wrote:
As discussed some time ago, Berlios will switch off the SVN service by the end of the year and thus we must move.
I proposed to our SVN experts to start the move on 2011-11-29. This means, Berlios will be switched to a read-only state and we will start copying the files with all the history and revisions to opensuse.org. This will probably take some days.
Do you have any concerns about the timing and the procedure? For openSUSE, we still have the possibility to finish the currect release notes and do other online updates, if needed. For SLE 11 SP2, we can prepare the RC2 release as planned.
ATM, I do not know how we can preserve the accounts or the account names. Stay tuned...
An alternative is switching to github.com. Besides git it supports svn - and also editing of files via the web.
All this are too technical for me so I have one question, will we be able to continue work with Vertaal after the changes? it is far the most practical tool we found ;-)
Andreas
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
2011/11/17 Kostas Koudaras warlordfff@gmail.com:
2011/11/17 Andreas Jaeger aj@suse.com:
An alternative is switching to github.com. Besides git it supports svn - and also editing of files via the web.
All this are too technical for me so I have one question, will we be able to continue work with Vertaal after the changes?
Also for me this is too technical. My questions are: with git can we still checkout/commit/update only our specific language in order to save time/space/bandwidth?
Best, Andrea
On Thursday, November 17, 2011 12:30:58 Andrea Turrini wrote:
2011/11/17 Kostas Koudaras warlordfff@gmail.com:
2011/11/17 Andreas Jaeger aj@suse.com:
An alternative is switching to github.com. Besides git it supports svn - and also editing of files via the web.
All this are too technical for me so I have one question, will we be able to continue work with Vertaal after the changes?
Also for me this is too technical. My questions are: with git can we still checkout/commit/update only our specific language in order to save time/space/bandwidth?
Thomas, can you answer that?
Note: I'm just offering an alternative - you have to use the tools ;)
Andreas
On Thu, Nov 17, 2011 at 8:51 AM, Andreas Jaeger aj@suse.com wrote:
All this are too technical for me so I have one question, will we be able to continue work with Vertaal after the changes?
Also for me this is too technical. My questions are: with git can we still checkout/commit/update only our specific language in order to save time/space/bandwidth?
Actually no. Even with git sparse checkout, you still need to clone the whole repository.
Git is great for devs, but for translators with no dev background, it would be a bit difficult to understand.
Regarding Vertaal, it doesn't support git.
Στις 17/11/2011 02:04 μμ, ο/η Gabriel [SGT] έγραψε:
On Thu, Nov 17, 2011 at 8:51 AM, Andreas Jaegeraj@suse.com wrote:
All this are too technical for me so I have one question, will we be able to continue work with Vertaal after the changes?
Also for me this is too technical. My questions are: with git can we still checkout/commit/update only our specific language in order to save time/space/bandwidth?
Actually no. Even with git sparse checkout, you still need to clone the whole repository.
Git is great for devs, but for translators with no dev background, it would be a bit difficult to understand.
Regarding Vertaal, it doesn't support git.
So if we move to svn.opensuse then Vertaal can be used like BerliOS, right?
2011/11/17 Stathis Iosifidis (aka diamond_gr) diamond_gr@freemail.gr:
So if we move to svn.opensuse then Vertaal can be used like BerliOS, right?
That's right.
stop writting to me please I have nothing to do with you !!! Thank you to stop !!!
----- Original Message ----- From: "Gabriel [SGT]" gabriel@opensuse.org To: "OS-trans" opensuse-translation@opensuse.org Sent: Thursday, November 17, 2011 1:28 PM Subject: Re: [opensuse-translation] Moving SVN to opensuse.org
2011/11/17 Stathis Iosifidis (aka diamond_gr) diamond_gr@freemail.gr:
So if we move to svn.opensuse then Vertaal can be used like BerliOS, right?
That's right.
-- Kind Regards -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
stop writting to me please I have nothing to do with you !!! Thank you to stop !!!
----- Original Message ----- From: "Stathis Iosifidis (aka diamond_gr)" diamond_gr@freemail.gr To: opensuse-translation@opensuse.org Sent: Thursday, November 17, 2011 1:24 PM Subject: Re: [opensuse-translation] Moving SVN to opensuse.org
Στις 17/11/2011 02:04 μμ, ο/η Gabriel [SGT] έγραψε:
On Thu, Nov 17, 2011 at 8:51 AM, Andreas Jaegeraj@suse.com wrote:
All this are too technical for me so I have one question, will we be able to continue work with Vertaal after the changes?
Also for me this is too technical. My questions are: with git can we still checkout/commit/update only our specific language in order to save time/space/bandwidth?
Actually no. Even with git sparse checkout, you still need to clone the whole repository.
Git is great for devs, but for translators with no dev background, it would be a bit difficult to understand.
Regarding Vertaal, it doesn't support git.
So if we move to svn.opensuse then Vertaal can be used like BerliOS, right? -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
stop writting to me please I have nothing to do with you !!! Thank you to stop !!!
----- Original Message ----- From: "Gabriel [SGT]" gabriel@opensuse.org To: "OS-trans" opensuse-translation@opensuse.org Sent: Thursday, November 17, 2011 1:04 PM Subject: Re: [opensuse-translation] Moving SVN to opensuse.org
On Thu, Nov 17, 2011 at 8:51 AM, Andreas Jaeger aj@suse.com wrote:
All this are too technical for me so I have one question, will we be able to continue work with Vertaal after the changes?
Also for me this is too technical. My questions are: with git can we still checkout/commit/update only our specific language in order to save time/space/bandwidth?
Actually no. Even with git sparse checkout, you still need to clone the whole repository.
Git is great for devs, but for translators with no dev background, it would be a bit difficult to understand.
Regarding Vertaal, it doesn't support git.
-- Kind Regards -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
On 17.11.2011 12:51, Andreas Jaeger wrote:
On Thursday, November 17, 2011 12:30:58 Andrea Turrini wrote:
2011/11/17 Kostas Koudaraswarlordfff@gmail.com:
2011/11/17 Andreas Jaegeraj@suse.com:
An alternative is switching to github.com. Besides git it supports svn - and also editing of files via the web.
All this are too technical for me so I have one question, will we be able to continue work with Vertaal after the changes?
Also for me this is too technical. My questions are: with git can we still checkout/commit/update only our specific language in order to save time/space/bandwidth?
Thomas, can you answer that?
Note: I'm just offering an alternative - you have to use the tools ;)
No, with git you can't only checkout your language. But github offers also svn access to its repos: https://github.com/blog/966-improved-subversion-client-support with that you would be able to checkout only your language for example.
I'm not sure how well committing from such a partial svn checkout works, that would need to be tested.
Greetings
stop writting to me please I have nothing to do with you !!! Thank you to stop !!!
----- Original Message ----- From: "Thomas Schmidt" tom@opensuse.org To: opensuse-translation@opensuse.org Sent: Thursday, November 17, 2011 1:31 PM Subject: Re: [opensuse-translation] Moving SVN to opensuse.org
On 17.11.2011 12:51, Andreas Jaeger wrote:
On Thursday, November 17, 2011 12:30:58 Andrea Turrini wrote:
2011/11/17 Kostas Koudaraswarlordfff@gmail.com:
2011/11/17 Andreas Jaegeraj@suse.com:
An alternative is switching to github.com. Besides git it supports svn - and also editing of files via the web.
All this are too technical for me so I have one question, will we be able to continue work with Vertaal after the changes?
Also for me this is too technical. My questions are: with git can we still checkout/commit/update only our specific language in order to save time/space/bandwidth?
Thomas, can you answer that?
Note: I'm just offering an alternative - you have to use the tools ;)
No, with git you can't only checkout your language. But github offers also svn access to its repos: https://github.com/blog/966-improved-subversion-client-support with that you would be able to checkout only your language for example.
I'm not sure how well committing from such a partial svn checkout works, that would need to be tested.
Greetings
-- Thomas Schmidt (tom [at] opensuse.org) openSUSE Boosters Team "Don't Panic", Douglas Adams (11.03.1952 - 11.05.2001) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
stop writting to me please I have nothing to do with you !!! Thank you to stop !!!
----- Original Message ----- From: "Andreas Jaeger" aj@suse.com To: opensuse-translation@opensuse.org Cc: "Andrea Turrini" andrea.turrini@gmail.com; tschmidt@suse.de Sent: Thursday, November 17, 2011 12:51 PM Subject: Re: [opensuse-translation] Moving SVN to opensuse.org
On Thursday, November 17, 2011 12:30:58 Andrea Turrini wrote:
2011/11/17 Kostas Koudaras warlordfff@gmail.com:
2011/11/17 Andreas Jaeger aj@suse.com:
An alternative is switching to github.com. Besides git it supports svn - and also editing of files via the web.
All this are too technical for me so I have one question, will we be able to continue work with Vertaal after the changes?
Also for me this is too technical. My questions are: with git can we still checkout/commit/update only our specific language in order to save time/space/bandwidth?
Thomas, can you answer that?
Note: I'm just offering an alternative - you have to use the tools ;)
Andreas
stop writting to me please I have nothing to do with you !!! Thank you to stop !!!
----- Original Message ----- From: "Andrea Turrini" andrea.turrini@gmail.com To: "OS-trans" opensuse-translation@opensuse.org Sent: Thursday, November 17, 2011 12:30 PM Subject: Re: [opensuse-translation] Moving SVN to opensuse.org
2011/11/17 Kostas Koudaras warlordfff@gmail.com:
2011/11/17 Andreas Jaeger aj@suse.com:
An alternative is switching to github.com. Besides git it supports svn - and also editing of files via the web.
All this are too technical for me so I have one question, will we be able to continue work with Vertaal after the changes?
Also for me this is too technical. My questions are: with git can we still checkout/commit/update only our specific language in order to save time/space/bandwidth?
Best, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
stop writting to me please I have nothing to do with you !!! Thank you to stop !!!
----- Original Message ----- From: "Kostas Koudaras" warlordfff@gmail.com To: "Andreas Jaeger" aj@suse.com Cc: opensuse-translation@opensuse.org; swims@novell.com; pdillon@novell.com Sent: Thursday, November 17, 2011 12:07 PM Subject: Re: [opensuse-translation] Moving SVN to opensuse.org
2011/11/17 Andreas Jaeger aj@suse.com:
On Thursday, November 17, 2011 09:54:22 Karl Eichwalder wrote:
As discussed some time ago, Berlios will switch off the SVN service by the end of the year and thus we must move.
I proposed to our SVN experts to start the move on 2011-11-29. This means, Berlios will be switched to a read-only state and we will start copying the files with all the history and revisions to opensuse.org. This will probably take some days.
Do you have any concerns about the timing and the procedure? For openSUSE, we still have the possibility to finish the currect release notes and do other online updates, if needed. For SLE 11 SP2, we can prepare the RC2 release as planned.
ATM, I do not know how we can preserve the accounts or the account names. Stay tuned...
An alternative is switching to github.com. Besides git it supports svn - and also editing of files via the web.
All this are too technical for me so I have one question, will we be able to continue work with Vertaal after the changes? it is far the most practical tool we found ;-)
Andreas
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
2011/11/17 Andreas Jaeger aj@suse.com:
On Thursday, November 17, 2011 09:54:22 Karl Eichwalder wrote: An alternative is switching to github.com. Besides git it supports svn - and also editing of files via the web.
[reposting, the first answer only got to Andreas; sorry for that] Yes, I remember this has been brought up at some point. Speaking for the Romanian translators, I'm against that for the moment for several reasons:
- not all translators are technical (see Kosta's response :D ) - for then SVN or git makes no difference - some tools only support SVN at the moment (we're using Narro, which allows automatic SVN and Mercurial uploads, but no git)
Also, if we could have PKI authentication on the new host, that would be great - the same Narro limitations :)
Thanks, Strainu
2011/11/17 Strainu strainu10@gmail.com:
2011/11/17 Andreas Jaeger aj@suse.com:
On Thursday, November 17, 2011 09:54:22 Karl Eichwalder wrote: An alternative is switching to github.com. Besides git it supports svn - and also editing of files via the web.
[reposting, the first answer only got to Andreas; sorry for that] Yes, I remember this has been brought up at some point. Speaking for the Romanian translators, I'm against that for the moment for several reasons:
- not all translators are technical (see Kosta's response :D ) - for then SVN or git makes no difference - some tools only support SVN at the moment (we're using Narro, which allows automatic SVN and Mercurial uploads, but no git)
Also, if we could have PKI authentication on the new host, that would be great - the same Narro limitations :)
So the way I see things since afaik many of the translators don't have the knowledge to use other tools that are 'based'/support SVN, then maybe the people who will actually work for the change take that in mind and if it is not so much work or trouble to make it on SVN. In any way don't take it as a demand or something, I don't want to be rude and I really respect the people who work on solving this problem.
Thanks, Strainu -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Kostas
stop writting to me please I have nothing to do with you !!! Thank you to stop !!!
----- Original Message ----- From: "Kostas Koudaras" warlordfff@gmail.com To: "Strainu" strainu10@gmail.com Cc: "Andreas Jaeger" aj@suse.com; opensuse-translation@opensuse.org; swims@novell.com; pdillon@novell.com Sent: Thursday, November 17, 2011 2:34 PM Subject: Re: [opensuse-translation] Moving SVN to opensuse.org
2011/11/17 Strainu strainu10@gmail.com:
2011/11/17 Andreas Jaeger aj@suse.com:
On Thursday, November 17, 2011 09:54:22 Karl Eichwalder wrote: An alternative is switching to github.com. Besides git it supports svn - and also editing of files via the web.
[reposting, the first answer only got to Andreas; sorry for that] Yes, I remember this has been brought up at some point. Speaking for the Romanian translators, I'm against that for the moment for several reasons:
- not all translators are technical (see Kosta's response :D ) - for
then SVN or git makes no difference
- some tools only support SVN at the moment (we're using Narro, which
allows automatic SVN and Mercurial uploads, but no git)
Also, if we could have PKI authentication on the new host, that would be great - the same Narro limitations :)
So the way I see things since afaik many of the translators don't have the knowledge to use other tools that are 'based'/support SVN, then maybe the people who will actually work for the change take that in mind and if it is not so much work or trouble to make it on SVN. In any way don't take it as a demand or something, I don't want to be rude and I really respect the people who work on solving this problem.
Thanks, Strainu -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Kostas
Strainu strainu10@gmail.com writes:
2011/11/17 Andreas Jaeger aj@suse.com:
On Thursday, November 17, 2011 09:54:22 Karl Eichwalder wrote: An alternative is switching to github.com. Besides git it supports svn - and also editing of files via the web.
- not all translators are technical (see Kosta's response :D ) - for
then SVN or git makes no difference
- some tools only support SVN at the moment (we're using Narro, which
allows automatic SVN and Mercurial uploads, but no git)
github is a nice place and directly editing with a webbrowser is a rather convenient feature. But to avoid compatibility trouble we probably better stick with a plain SVN server for the moment. Thus I also vote to migrate to svn.opensuse.org on 2011-11-29 and the following days.
Also, if we could have PKI authentication on the new host, that would be great - the same Narro limitations :)
I'm not sure about it, but since svn.opensuse.org is maintained by opensuse admin, it should be possible to add useful feature (no promisses how when this could be done).
stop writting to me please I have nothing to do with you !!! Thank you to stop !!!
----- Original Message ----- From: "Karl Eichwalder" ke@suse.de To: "Strainu" strainu10@gmail.com Cc: "Andreas Jaeger" aj@suse.com; opensuse-translation@opensuse.org; swims@novell.com; pdillon@novell.com Sent: Thursday, November 17, 2011 3:12 PM Subject: Re: [opensuse-translation] Moving SVN to opensuse.org
Strainu strainu10@gmail.com writes:
2011/11/17 Andreas Jaeger aj@suse.com:
On Thursday, November 17, 2011 09:54:22 Karl Eichwalder wrote: An alternative is switching to github.com. Besides git it supports svn - and also editing of files via the web.
- not all translators are technical (see Kosta's response :D ) - for
then SVN or git makes no difference
- some tools only support SVN at the moment (we're using Narro, which
allows automatic SVN and Mercurial uploads, but no git)
github is a nice place and directly editing with a webbrowser is a rather convenient feature. But to avoid compatibility trouble we probably better stick with a plain SVN server for the moment. Thus I also vote to migrate to svn.opensuse.org on 2011-11-29 and the following days.
Also, if we could have PKI authentication on the new host, that would be great - the same Narro limitations :)
I'm not sure about it, but since svn.opensuse.org is maintained by opensuse admin, it should be possible to add useful feature (no promisses how when this could be done).
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-11-17 15:12, Karl Eichwalder wrote:
github is a nice place and directly editing with a webbrowser is a rather convenient feature.
A useless feature for translating .po files. And as vertaal does not support git, that would be goodby for me.
- -- Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
stop writting to me please I have nothing to do with you !!! Thank you to stop !!!
----- Original Message ----- From: "Carlos E. R." carlos.e.r@opensuse.org To: "os-trans" opensuse-translation@opensuse.org Sent: Thursday, November 17, 2011 3:45 PM Subject: Re: [opensuse-translation] Moving SVN to opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-11-17 15:12, Karl Eichwalder wrote:
github is a nice place and directly editing with a webbrowser is a rather convenient feature.
A useless feature for translating .po files. And as vertaal does not support git, that would be goodby for me.
Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAk7FHfQACgkQtTMYHG2NR9Uo4QCfb03ShT9xuV/kaRaMRlAEx7Ry i3wAn0sN8c91SrrfdgPOcQOwhSov9ndP =99ne
-----END PGP SIGNATURE-----
To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
On 11/17/2011 03:12 PM, Karl Eichwalder wrote:
Also, if we could have PKI authentication on the new host, that would be great - the same Narro limitations :)
I'm not sure about it, but since svn.opensuse.org is maintained by opensuse admin, it should be possible to add useful feature (no promisses how when this could be done).
A feature I find useful in berliOS is the mail sent on commit. So it is enough to check mails in order to know when the local copy needs to be updated.
I hope this feature can be kept, perhaps without the output of svn diff in the body of the mail.
Best, Andrea
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thursday, 2011-11-17 at 20:41 +0100, Andrea Turrini wrote:
A feature I find useful in berliOS is the mail sent on commit. So it is enough to check mails in order to know when the local copy needs to be updated.
I disabled that.
I simply update whenever I'm going to start translating a file.
- -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
2011/11/17 Carlos E. R. robin.listas@telefonica.net:
A feature I find useful in berliOS is the mail sent on commit. So it is enough to check mails in order to know when the local copy needs to be updated.
I disabled that.
Your choice and I hope that, if implemented also in the new svn server, you can still disable it.
I simply update whenever I'm going to start translating a file.
I too, but if my files are fully translated, usually I do not perform an svn up every day to check whether they are still translated but I do it only when I receive a notification about possible changes.
Best, Andrea
On vrijdag 18 november 2011 09:41:55 Andrea Turrini wrote:
2011/11/17 Carlos E. R. robin.listas@telefonica.net:
A feature I find useful in berliOS is the mail sent on commit. So it is enough to check mails in order to know when the local copy needs to be updated.
I disabled that.
Your choice and I hope that, if implemented also in the new svn server, you can still disable it.
I simply update whenever I'm going to start translating a file.
I too, but if my files are fully translated, usually I do not perform an svn up every day to check whether they are still translated but I do it only when I receive a notification about possible changes.
In the SVN for KDE translations one can set a filter on the files one wants to receive a report on. In fact one gets the message on the whole commit that tests positive on that filter. Something like that would be nice.
2011/11/18 Freek de Kruijf f.de.kruijf@gmail.com:
On vrijdag 18 november 2011 09:41:55 Andrea Turrini wrote:
2011/11/17 Carlos E. R. robin.listas@telefonica.net:
A feature I find useful in berliOS is the mail sent on commit. So it is enough to check mails in order to know when the local copy needs to be updated.
I disabled that.
Your choice and I hope that, if implemented also in the new svn server, you can still disable it.
I simply update whenever I'm going to start translating a file.
I too, but if my files are fully translated, usually I do not perform an svn up every day to check whether they are still translated but I do it only when I receive a notification about possible changes.
If you use Vertaal it sends you a mail whenever a file changes or need to be merged (at least for team coordinators)
Regards,
Luiz
Andrea Turrini andrea.turrini@gmail.com writes:
A feature I find useful in berliOS is the mail sent on commit. So it is enough to check mails in order to know when the local copy needs to be updated.
It should be possible.
I hope this feature can be kept, perhaps without the output of svn diff in the body of the mail.
We will check it out.
stop writting to me please I have nothing to do with you !!! Thank you to stop !!!
----- Original Message ----- From: "Strainu" strainu10@gmail.com To: "Andreas Jaeger" aj@suse.com Cc: opensuse-translation@opensuse.org; swims@novell.com; pdillon@novell.com Sent: Thursday, November 17, 2011 2:06 PM Subject: Re: [opensuse-translation] Moving SVN to opensuse.org
2011/11/17 Andreas Jaeger aj@suse.com:
On Thursday, November 17, 2011 09:54:22 Karl Eichwalder wrote: An alternative is switching to github.com. Besides git it supports svn - and also editing of files via the web.
[reposting, the first answer only got to Andreas; sorry for that] Yes, I remember this has been brought up at some point. Speaking for the Romanian translators, I'm against that for the moment for several reasons:
- not all translators are technical (see Kosta's response :D ) - for
then SVN or git makes no difference
- some tools only support SVN at the moment (we're using Narro, which
allows automatic SVN and Mercurial uploads, but no git)
Also, if we could have PKI authentication on the new host, that would be great - the same Narro limitations :)
Thanks, Strainu -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
stop writting to me please I have nothing to do with you !!! Thank you to stop !!!
----- Original Message ----- From: "Andreas Jaeger" aj@suse.com To: opensuse-translation@opensuse.org; swims@novell.com Cc: pdillon@novell.com Sent: Thursday, November 17, 2011 12:03 PM Subject: Re: [opensuse-translation] Moving SVN to opensuse.org
On Thursday, November 17, 2011 09:54:22 Karl Eichwalder wrote:
As discussed some time ago, Berlios will switch off the SVN service by the end of the year and thus we must move.
I proposed to our SVN experts to start the move on 2011-11-29. This means, Berlios will be switched to a read-only state and we will start copying the files with all the history and revisions to opensuse.org. This will probably take some days.
Do you have any concerns about the timing and the procedure? For openSUSE, we still have the possibility to finish the currect release notes and do other online updates, if needed. For SLE 11 SP2, we can prepare the RC2 release as planned.
ATM, I do not know how we can preserve the accounts or the account names. Stay tuned...
An alternative is switching to github.com. Besides git it supports svn - and also editing of files via the web.
Andreas
On 17/11/2011 10:54 πμ, Karl Eichwalder wrote:
As discussed some time ago, Berlios will switch off the SVN service by the end of the year and thus we must move.
Hallelujah
2011/11/17 Karl Eichwalder ke@suse.de:
I proposed to our SVN experts to start the move on 2011-11-29. This means, Berlios will be switched to a read-only state and we will start copying the files with all the history and revisions to opensuse.org. This will probably take some days.
............................
ATM, I do not know how we can preserve the accounts or the account names. Stay tuned...
Today is 2011-11-29, any status updates, please, Karl? =)
Le 29/11/2011 12:29, Alexander Melentyev a écrit :
2011/11/17 Karl Eichwalderke@suse.de:
I proposed to our SVN experts to start the move on 2011-11-29. This means, Berlios will be switched to a read-only state and we will start copying the files with all the history and revisions to opensuse.org. This will probably take some days.
............................
ATM, I do not know how we can preserve the accounts or the account names. Stay tuned...
Today is 2011-11-29, any status updates, please, Karl? =)
opensuse-doc had already moved, so if you (Karl or other SVN experts) have any question you can ask the doc team.
Guillaume
Guillaume Gardet guillaume.gardet@free.fr writes:
opensuse-doc had already moved, so if you (Karl or other SVN experts) have any question you can ask the doc team.
Yes, Juergen already offered help :-)
Alexander Melentyev minton@opensuse.org writes:
2011/11/17 Karl Eichwalder ke@suse.de:
I proposed to our SVN experts to start the move on 2011-11-29. This means, Berlios will be switched to a read-only state and we will start copying the files with all the history and revisions to opensuse.org. This will probably take some days.
............................
ATM, I do not know how we can preserve the accounts or the account names. Stay tuned...
Today is 2011-11-29, any status updates, please, Karl? =)
Yes, thanks for asking ;) I was about to post later the day--rather late, I know.
The guys who wanted to help with the migration are only partially available right now. And, maybe more interesting, Berlios seems to recover: http://developer.berlios.de/forum/forum.php?forum_id=37533
I'd like to hear your comments.
Le 29/11/2011 13:55, Karl Eichwalder a écrit :
Alexander Melentyevminton@opensuse.org writes:
2011/11/17 Karl Eichwalderke@suse.de:
I proposed to our SVN experts to start the move on 2011-11-29. This means, Berlios will be switched to a read-only state and we will start copying the files with all the history and revisions to opensuse.org. This will probably take some days.
............................
ATM, I do not know how we can preserve the accounts or the account names. Stay tuned...
Today is 2011-11-29, any status updates, please, Karl? =)
Yes, thanks for asking ;) I was about to post later the day--rather late, I know.
The guys who wanted to help with the migration are only partially available right now. And, maybe more interesting, Berlios seems to recover: http://developer.berlios.de/forum/forum.php?forum_id=37533
I'd like to hear your comments.
I think we should host openSUSE projects on our own servers to be able to do what we want and get rid of external servers problems (like BerliOS shutdown). If BerliOS servers do not close right now, maybe they will close in a few months, nobody knows.
So it makes sense to host i18n things on svn.opensuse.org.
It is my point of view.
Guillaume
2011/11/29 Guillaume Gardet guillaume.gardet@free.fr:
I think we should host openSUSE projects on our own servers to be able to do what we want and get rid of external servers problems (like BerliOS shutdown). If BerliOS servers do not close right now, maybe they will close in a few months, nobody knows.
So it makes sense to host i18n things on svn.opensuse.org.
It is my point of view.
Guillaume
I totally agree with that. The fact Berlios is not getting shut down right now proves nothing, anything can happen. It's like sitting on a gun powder barrell. Moving to svn.opensuse.org makes a lot of sense to me.
Regards, Minton.
Alexander Melentyev minton@opensuse.org writes:
I totally agree with that. The fact Berlios is not getting shut down right now proves nothing, anything can happen. It's like sitting on a gun powder barrell. Moving to svn.opensuse.org makes a lot of sense to me.
Yes, it mostly looks the same to me.
But Berlios offers some features that opensuse.org currently does not:
svn+ssh is not available
adding new users is a rather manual process
Both features are probably not that important for us.
Le 29/11/2011 14:56, Karl Eichwalder a écrit :
Alexander Melentyevminton@opensuse.org writes:
I totally agree with that. The fact Berlios is not getting shut down right now proves nothing, anything can happen. It's like sitting on a gun powder barrell. Moving to svn.opensuse.org makes a lot of sense to me.
Yes, it mostly looks the same to me.
But Berlios offers some features that opensuse.org currently does not:
svn+ssh is not available adding new users is a rather manual processBoth features are probably not that important for us.
Maybe, missing features can be added later if necessary?
https is available, so svn+ssh is really needed?
Adding new users is your process (karl) ;) , but I think adding users is not done very often.
Cheers,
Guillaume
Le 29/11/2011 15:39, Strainu a écrit :
https is available, so svn+ssh is really needed?
Right now, it is, at least for the ro team.
Could you explain why, please?
Karl, how difficult is it to add svn+ssh feature to our server?
Cheers,
Guillaume
2011/11/29 Guillaume Gardet guillaume.gardet@free.fr:
Le 29/11/2011 15:39, Strainu a écrit :
https is available, so svn+ssh is really needed?
Right now, it is, at least for the ro team.
Could you explain why, please?
We're using an automatic submission tool that only supports ssh+svn ATM. This could of course be fixed, but it takes time that the developer of the tool does not really have. It could take several months before this is fixed.
Strainu
On Tue, Nov 29, 2011 at 11:55 AM, Strainu strainu10@gmail.com wrote:
We're using an automatic submission tool that only supports ssh+svn ATM. This could of course be fixed, but it takes time that the developer of the tool does not really have. It could take several months before this is fixed.
You could move to vertaal.
2011/11/29 Gabriel [SGT] gabriel@opensuse.org:
On Tue, Nov 29, 2011 at 11:55 AM, Strainu strainu10@gmail.com wrote:
We're using an automatic submission tool that only supports ssh+svn ATM. This could of course be fixed, but it takes time that the developer of the tool does not really have. It could take several months before this is fixed.
You could move to vertaal.
We thought about that, but decided against it, as it would mean loosing the suggestions from the other projects. Nobody translates in Romanian using Vertaal.
Plus, as far as the content goes, this is not free software, and that would discourage some of our contributors.
Strainu
On Tue, Nov 29, 2011 at 12:23 PM, Strainu strainu10@gmail.com wrote:
We thought about that, but decided against it, as it would mean loosing the suggestions from the other projects. Nobody translates in Romanian using Vertaal.
Plus, as far as the content goes, this is not free software, and that would discourage some of our contributors.
https://github.com/dahool/vertaal https://github.com/dahool/vertaal/blob/master/LICENSE.txt
2011/11/29 Gabriel [SGT] gabriel@opensuse.org:
On Tue, Nov 29, 2011 at 12:23 PM, Strainu strainu10@gmail.com wrote:
We thought about that, but decided against it, as it would mean loosing the suggestions from the other projects. Nobody translates in Romanian using Vertaal.
Plus, as far as the content goes, this is not free software, and that would discourage some of our contributors.
https://github.com/dahool/vertaal https://github.com/dahool/vertaal/blob/master/LICENSE.txt
That's the code. The glossary says: cc-by-nc-sa-3.0 [ http://www.vertaal.com.ar/iterm/opensuse/ro/list/ ], which is non-free. The single most important reason for having an online translation tool is collaboration and standardization between projects. If I cannot use the translations proposed by other people, I don't see much use in working online.
Regards, Strainu
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-11-29 17:01, Strainu wrote:
That's the code. The glossary says: cc-by-nc-sa-3.0 [ http://www.vertaal.com.ar/iterm/opensuse/ro/list/ ],
Creativecommons is a free license, and it applies to the words you add to the glossary.
- -- Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
2011/11/29 Karl Eichwalder ke@suse.de:
Alexander Melentyev minton@opensuse.org writes:
I totally agree with that. The fact Berlios is not getting shut down right now proves nothing, anything can happen. It's like sitting on a gun powder barrell. Moving to svn.opensuse.org makes a lot of sense to me.
Yes, it mostly looks the same to me.
But Berlios offers some features that opensuse.org currently does not:
I don't want to monopolize this thread, but I was very busy when the translation project first moved to berlios and I can't find the relevant mails in the archive. Could someone remind us why did this change happen in the first place? Was it because of these missing features? If so, perhaps they were really important at the time.
Sorry for the many emails I've sent today, some of them quite offtopic. Strainu
Strainu strainu10@gmail.com writes:
I don't want to monopolize this thread, but I was very busy when the translation project first moved to berlios and I can't find the relevant mails in the archive. Could someone remind us why did this change happen in the first place?
We move from Novell Forge to Berlios because Novell Forge closed doors. But Novell Forge also supported svn+ssh. Some guys were using it (because https did not work for them; I think, if we tried harder, we could have made https also work for them).
I think svn+ssh is marginally faster (less overhead) than https.
Was it because of these missing features? If so, perhaps they were really important at the time.
Up til now it is unclear, whether svn+ssh will become available. It would mean some kind of shell access or, at least, more binaries on the svn server, which the admin were happy to avoid thus far.
Sorry for the many emails I've sent today, some of them quite offtopic.
It pretty ok to exchange argument, esp. because the actual move may take a little bit longer (as said yesterday).
Now it is for real. Tomorrow, we'd like to move from Berlios to opensuse.org; Daniel is available again, and will do the magic step.
The plan is, to switch the Berlios SVN to read-only on Wednesday, 2011-12-07 16:00 CET. During Thursday, we want to continue as usual on opensuse.org with the same user names and passwords as on Berlios.
Karl Eichwalder ke@suse.de writes:
Now it is for real. Tomorrow, we'd like to move from Berlios to opensuse.org; Daniel is available again, and will do the magic step.
The plan is, to switch the Berlios SVN to read-only on Wednesday, 2011-12-07 16:00 CET. During Thursday, we want to continue as usual on opensuse.org with the same user names and passwords as on Berlios.
BTW, if wanted we can do a user name renaming. E.g., we can switch your Berlios name to your opensuse account name. (the password will be independent from your "real" opensuse account!).
Karl Eichwalder ke@suse.de writes:
Now it is for real. Tomorrow, we'd like to move from Berlios to opensuse.org; Daniel is available again, and will do the magic step.
The plan is, to switch the Berlios SVN to read-only on Wednesday, 2011-12-07 16:00 CET. During Thursday, we want to continue as usual on opensuse.org with the same user names and passwords as on Berlios.
Short info update: We (thanks to Daniel!) successfully dumped and downloaded the data from Berlios and started to rebuild the SVN repo at https://svn.opensuse.org/svn/opensuse-i18n --it takes a bit longer than initially expected. We can probably enable the repo tomorrow during the day.
Then I'd appreciate if you could help me with checking the contents. At least, we must make sure that the current versions are properly migrated. But it was our intention to restore all revisions and the complete history.
On 12/08/2011 05:45 PM, Karl Eichwalder wrote:
Short info update: We (thanks to Daniel!) successfully dumped and downloaded the data from Berlios and started to rebuild the SVN repo at https://svn.opensuse.org/svn/opensuse-i18n --it takes a bit longer than initially expected. We can probably enable the repo tomorrow during the day.
Very good!
Then I'd appreciate if you could help me with checking the contents. At least, we must make sure that the current versions are properly migrated. But it was our intention to restore all revisions and the complete history.
I can check Italian content: I will checkout the new repo and then I will do a diff between old and new files provided that I remember the password I set for svn (since I set up public key encryption on ssh+svn for berlios). In case I will contact you directly for a password reset.
Best, Andrea
Andrea Turrini andrea.turrini@gmail.com writes:
On 12/08/2011 05:45 PM, Karl Eichwalder wrote:
Short info update: We (thanks to Daniel!) successfully dumped and downloaded the data from Berlios and started to rebuild the SVN repo at https://svn.opensuse.org/svn/opensuse-i18n --it takes a bit longer than initially expected. We can probably enable the repo tomorrow during the day.
The move is done and the new repo is writable.
Then I'd appreciate if you could help me with checking the contents. At least, we must make sure that the current versions are properly migrated. But it was our intention to restore all revisions and the complete history.
I can check Italian content: I will checkout the new repo and then I will do a diff between old and new files provided that I remember the password I set for svn (since I set up public key encryption on ssh+svn for berlios). In case I will contact you directly for a password reset.
Thanks for offering help! In case you want to reset your password, create a new one as follows (without salt):
perl print crypt("password", "$1$"),"\n"; ^D
"^D" means Ctrl-D. Once pressed, you will see the string in your terminal. Send this to me together with your SVN user name.
Karl Eichwalder ke@suse.de writes:
Thanks for offering help! In case you want to reset your password, create a new one as follows (without salt):
perl print crypt("password", "$1$"),"\n"; ^D
"^D" means Ctrl-D. Once pressed, you will see the string in your terminal. Send this to me together with your SVN user name.
I forgot to mention: you can usually find your password in of the auth files:
cd ~/.subversion/auth grep berlios */*
Then check the file it prints.
Hi,
Le 08/12/2011 17:45, Karl Eichwalder a écrit :
Karl Eichwalderke@suse.de writes:
Now it is for real. Tomorrow, we'd like to move from Berlios to opensuse.org; Daniel is available again, and will do the magic step.
The plan is, to switch the Berlios SVN to read-only on Wednesday, 2011-12-07 16:00 CET. During Thursday, we want to continue as usual on opensuse.org with the same user names and passwords as on Berlios.
Short info update: We (thanks to Daniel!) successfully dumped and downloaded the data from Berlios and started to rebuild the SVN repo at https://svn.opensuse.org/svn/opensuse-i18n --it takes a bit longer than initially expected. We can probably enable the repo tomorrow during the day.
Then I'd appreciate if you could help me with checking the contents. At least, we must make sure that the current versions are properly migrated. But it was our intention to restore all revisions and the complete history.
I checked trunk for french and there are no diff.
Cheers,
Guillaume
2011/12/9 Guillaume Gardet guillaume.gardet@free.fr
I checked trunk for french and there are no diff.
Also Italian is OK. And also commit works correctly.
Best, Andrea
On Fri, Dec 9, 2011 at 12:31 PM, Andrea Turrini andrea.turrini@gmail.com wrote:
2011/12/9 Guillaume Gardet guillaume.gardet@free.fr
I checked trunk for french and there are no diff.
Also Italian is OK. And also commit works correctly.
Best, Andrea
Vertaal is now using to the new svn infrastructure.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thursday, 2011-12-08 at 17:45 +0100, Karl Eichwalder wrote:
Short info update: We (thanks to Daniel!) successfully dumped and downloaded the data from Berlios and started to rebuild the SVN repo at https://svn.opensuse.org/svn/opensuse-i18n --it takes a bit longer than initially expected. We can probably enable the repo tomorrow during the day.
Something funny: it doesn't ask for my password.
cer@Telcontar:~/Projects/babel/SuSE/trunk> svn -N checkout https://robin_listas@svn.opensuse.org/svn/opensuse-i18n/trunk/lcn lcn A lcn/configure.ac A lcn/.svnignore.lang A lcn/.svnignore A lcn/README A lcn/.svnignore.po-dirs A lcn/Makefile.am U lcn Checked out revision 72705. cer@Telcontar:~/Projects/babel/SuSE/trunk>
- -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
On Fri, Feb 10, 2012 at 8:33 PM, Carlos E. R. robin.listas@telefonica.net wrote:
Something funny: it doesn't ask for my password.
Long time since I used svn, but I think it will ask for your password when you try to commit.
Kind Regards
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-02-11 00:44, Gabriel [SGT] wrote:
On Fri, Feb 10, 2012 at 8:33 PM, Carlos E. R. robin.listas@telefonica.net wrote:
Something funny: it doesn't ask for my password.
Long time since I used svn, but I think it will ask for your password when you try to commit.
I think it should ask for the password on the first, initial checkout. Then the password is saved locally, in "~/.subversion/auth/svn.ssl.server/*****", I think, and used for all subsequent connections.
I will try a small commit and see what happens, anyway.
Mmm... you are right, it asks on 1st commit. :-o
- -- Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Saturday, 2012-02-11 at 01:16 +0100, Carlos E. R. wrote:
On 2012-02-11 00:44, Gabriel [SGT] wrote:
Long time since I used svn, but I think it will ask for your password when you try to commit.
I think it should ask for the password on the first, initial checkout. Then the password is saved locally, in "~/.subversion/auth/svn.ssl.server/*****", I think, and used for all subsequent connections.
I will try a small commit and see what happens, anyway.
Mmm... you are right, it asks on 1st commit. :-o
Weird. Svn is asking for my password on every commit. This did not happen on berlios, it only asked once, and it was remembered for years. I did two commits in an hour, it asked twice.
- -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-04-06 04:16, Carlos E. R. wrote:
Weird. Svn is asking for my password on every commit. This did not happen on berlios, it only asked once, and it was remembered for years. I did two commits in an hour, it asked twice.
Found it.
~/.subversion/servers:
store-plaintext-passwords = yes
- -- Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
I know this is a bit off-topic, but there's something you might be interested:
"Version Control by Example" by Eric Sink
You ask for a free paper copy or any electronic format here:
* http://www.ericsink.com/vcbe/
It's really nice and useful for git, svn and mercurial.
Peace,´ NM
2012/2/10 Carlos E. R. robin.listas@telefonica.net:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thursday, 2011-12-08 at 17:45 +0100, Karl Eichwalder wrote:
Short info update: We (thanks to Daniel!) successfully dumped and downloaded the data from Berlios and started to rebuild the SVN repo at https://svn.opensuse.org/svn/opensuse-i18n --it takes a bit longer than initially expected. We can probably enable the repo tomorrow during the day.
Something funny: it doesn't ask for my password.
cer@Telcontar:~/Projects/babel/SuSE/trunk> svn -N checkout https://robin_listas@svn.opensuse.org/svn/opensuse-i18n/trunk/lcn lcn A lcn/configure.ac A lcn/.svnignore.lang A lcn/.svnignore A lcn/README A lcn/.svnignore.po-dirs A lcn/Makefile.am U lcn Checked out revision 72705. cer@Telcontar:~/Projects/babel/SuSE/trunk>
- -- Cheers,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux)
iEYEARECAAYFAk81qWUACgkQtTMYHG2NR9We0wCgh5M/48kRHpETElwEf+nOvTjf tfIAn3x7OMc4dX5l+HPoSvEwUovOQ5aW =vpjH
-----END PGP SIGNATURE-----
To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Hello,
I checked out a trunk repository from svn.opensuse.org and tried a test commit.
I'm quite sure I used the the same user name and password as before the repos were moved to Berlios, but the opensuse svn server does not accept this authentification.
So do I need to create a new svn user? If so where and how? Perhaps someone merely needs to grant my old user commit rights again?
Regards
Olav
Hi,
Le 16/02/2012 00:27, Olav P. a écrit :
Hello,
I checked out a trunk repository from svn.opensuse.org and tried a test commit.
I'm quite sure I used the the same user name and password as before the repos were moved to Berlios, but the opensuse svn server does not accept this authentification.
So do I need to create a new svn user? If so where and how? Perhaps someone merely needs to grant my old user commit rights again?
Karl should be able to help you.
Regards,
Guillaume
Regards
Olav
Guillaume Gardet guillaume.gardet@free.fr writes:
Le 16/02/2012 00:27, Olav P. a écrit :
I checked out a trunk repository from svn.opensuse.org and tried a test commit.
I'm quite sure I used the the same user name and password as before the repos were moved to Berlios, but the opensuse svn server does not accept this authentification.
So do I need to create a new svn user? If so where and how? Perhaps someone merely needs to grant my old user commit rights again?
The same password will; maybe, it is stored in one of the files in ~/.subversion/
I guess, you first checked it out anynomously, and then tried to do the checkin with your credentials. This never seems to work. Please, do a fresh checkout with your credentials, and then do a test commit.
If this fails again, we can reset your password.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-02-16 00:27, Olav P. wrote:
So do I need to create a new svn user? If so where and how? Perhaps someone merely needs to grant my old user commit rights again?
I checked out a fresh copy on an entirely new trunk tree out from svn.opensuse.org, I forgot the copy from berlios. You can reuse the tree from berlios if you remove all the .svn trees, and if the dates match. It's probably better to fetch the entire tree fresh.
And then, do it as you, not anonymous. I'm not sure this matters with svn, because the password is not requested till you commit.
- -- Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-11-29 14:56, Karl Eichwalder wrote:
But Berlios offers some features that opensuse.org currently does not:
svn+ssh is not available
When I use a command such as "svn up", am I using svn+ssh?
Because if I am (I do not know), then it is an issue for me.
- -- Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
On Tue, Nov 29, 2011 at 9:09 PM, Carlos E. R. carlos.e.r@opensuse.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-11-29 14:56, Karl Eichwalder wrote:
But Berlios offers some features that opensuse.org currently does not:
svn+ssh is not available
When I use a command such as "svn up", am I using svn+ssh?
Because if I am (I do not know), then it is an issue for me.
It depends, are you using https:// or svn+ssh:// ? I bet it's https :) Anyway, the subversion client can manage both. The access will be the same as it was when we started (https), using the opensuse svn.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-11-30 01:17, Gabriel [SGT] wrote:
On Tue, Nov 29, 2011 at 9:09 PM, Carlos E. R. <> wrote:
Because if I am (I do not know), then it is an issue for me.
It depends, are you using https:// or svn+ssh:// ? I bet it's https :) Anyway, the subversion client can manage both. The access will be the same as it was when we started (https), using the opensuse svn.
I see, it depends on how we originally called it. Let me see... I have a ~/.subversion dir... I see the "https://forgesvn1.novell.com:443" string, that's old. Ok, I see https://svn.berlios.de:443, then I have no problem.
- -- Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
translation@lists.opensuse.org
-
Alexander Melentyev -
Andrea Turrini -
Andreas Jaeger -
Carlos E. R. -
Carlos E. R. -
Freek de Kruijf -
Gabriel [SGT] -
Guillaume Gardet -
Herve DUPUIS -
Karl Eichwalder -
Kostas Boukouvalas -
Kostas Koudaras -
Luiz Fernando Ranghetti -
Nelson Marques -
Olav P. -
Stathis Iosifidis (aka diamond_gr) -
Strainu -
Thomas Schmidt