Onsdag 11. april 2012 16.35.38 skrev Carlos E. R.:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 2012-04-11 16:23, Olav P. wrote:

...

Hello guys and gals,

I have not commited any translations since Berlioz. So how do I get commit rights to the new translation repos?

The login/pass should be the same.

- -- Cheers / Saludos,

Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)

No it doesn't work. I have an old novell account i think I have used to commit translations in the past, but the login info for that account does not work. Olav P. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

Onsdag 11. april 2012 18.23.18 skrev Michael Skiba:

Am Mittwoch, 11. April 2012, 17:55:38 schrieb Olav P.:

...

No it doesn't work.

I have an old novell account i think I have used to commit translations in the past, but the login info for that account does not work.

I think what Carlos meant is that it uses the same login credentials from BerliOS, if you had an account there and were able to submit to the BerliOS- openSUSE-Repo. Did you have an account?

Regards, Michael

Yes, but i had a disk crash since then and those credentials were stored only in a virtual wallet. I'll try to retrieve the password from Berlios (I didn't think it would work anymore after the server switch). Thanks Olav -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

I got a new password from Berlios now and I can log in there. However, this Berlios username and password does not let me commit openSUSE translations.

Are you sure I do not need renewed commit rights after the move to svn.opensuse.org? Well as you said yourself, you got a NEW password from BerliOS. But the new opensuse-i18n-svn uses the one you had when they moved (I guess they just copied the svn auth file). So unless you can figure out what your BerliOS

Am Mittwoch, 11. April 2012, 18:58:06 schrieb Olav P.: password was before the move, you'll have to wait until Karl returns (probably during business hours tomorrow CEST) to send you a new one. But the waiting shouldn't be the problem, you can already check out the latest version of your language and start translating right away :) Regards, Michael

Olav Pettershagen writes:

I have checked out and updated from svn.opensuse.org (and translated) for quite a while :), only not been able to commit translations.

So I'm not really in a hurry. I'll ask Karl how to proceed one of these days.

Just send us an _encrypted_ password, that you would like to use for the opensuse SVN server. To encrypt the password, you can use the attached bash script as follows: Usage: ./svn-password <svn-repo> [<user-name>] Examples: This example uses the current login name as "user-name": ./svn-password opensuse-i18n This example sets "foobar123" as "user-name": ./svn-password opensuse-i18n foobar123 Please, send the _encrypted_ password directly to Daniel (see cc: jdsn@suse.de). -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)

...

Just send us an _encrypted_ password, that you would like to use for the opensuse SVN server. To encrypt the password, you can use the attached bash script as follows:

Usage: ./svn-password <svn-repo> [<user-name>]

Interesting method.

What it is not clear is what is the svn-repo, opensuse-i18n for all of us, or how we named the svn directory on our systems. This is a little script from Daniel Schmidt @ suse. In our case (the not- internal-suse-svn-repos?!) you give opensuse-i18n (or opensuse-doc) as a

Am Donnerstag, 12. April 2012, 11:54:14 schrieb Carlos E. R.: parameter for <svn-repo>, regardless how you named the repo on your local machine. It is purely for the script to distinguish between two different methods of creating a passwort: opensuse-i18n and opensuse-doc passwords are hashed with perls crypt() function, while any other passwords are hashed via md5. Regards, Michael