[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Arabic team coordinator
From:       "T.C. Hollingsworth" <tchollingsworth () gmail ! com>
Date:       2011-12-31 17:05:55
Message-ID: CAJVv0OnA-y2jYsSAbd4rQTA4s8rCa34_UZBFn_AJ7bTebV4UzQ () mail ! gmail ! com
[Download RAW message or body]

On Sat, Dec 31, 2011 at 9:36 AM, Abdalrahim Fakhouri
<abdilra7eem@gmail.com> wrote:

> On Sat, Dec 31, 2011 at 1:41 PM, <kde-i18n-doc-request@kde.org> wrote:
>>
>> > The command I used is:
>> > $ svn switch --username fakhouri
>> > https://svn.kde.org/home/kde/trunk/l10n-kde4/ar/messages/kde-runtime
>>
>> We do not use https anymore, you should use svn+ssh
>>
>> Albert
>
> I also tried the svn+ssh, and with both svn switch and svn checkout.

Make sure the SSH key on your system exists and matches the one in KDE identity.

First, run this command:
ssh-keygen -lf ~/.ssh/id_*sa

If that fails, you didn't set up SVN+SSH properly.  Follow the
instructions here to generate a key and configure SVN+SSH:
http://techbase.kde.org/Contribute/Get_a_Contributor_Account#SSH

Then, you can check it at identity.kde.org > Profile > Edit > Edit
public ssh keys...  If you do have a key, make sure the one there
matches the output of the command you just ran.  If it doesn't or you
just generated a new one, upload the correct id_rsa.pub here.  Then,
make sure to click "Save" on that screen and then "OK" on the profile
edit screen to save the changes, and then file a sysadmin request so
the keys get changed on the server:
https://bugs.kde.org/enter_sysadmin_request.cgi

A sysadmin will let you know when your keys are fixed and then
everything should work fine.

If your keys are set up properly, something strange might be going on
with your connection/firewall/etc.  Edit ~/.subversion/config,
uncomment (remove the hash [#] marks from the beginning of) the "ssh =
$SVN_SSH ssh -q" line in the "[tunnels]" section, and then remove the
"-q" from the end.  Save it, and try accessing KDE SVN+SSH again.
That config file change will cause SVN to print some debugging
information when trying to connect.  If you can't make any sense of
it, paste it in a reply here and maybe we can figure out what's going
on.

-T.C.
[prev in list] [next in list] [prev in thread] [next in thread]