How to commit to SVN?

Help
1

I recently followed the steps here to get a developer account. The goal was to be able to commit German translations to the i18n SVN repo located here. Until now, I checked out parts of this repo using the anonymous URL, worked on the translations and filed a Review Request on Phabricator so that my changes could be proofread by the German team.

I assumed, having a developer account now, I would be able to/should now use the Developer SVN URL (svn+ssh://svn@svn.kde.org/home/kde/trunk/l10n-support/de/summit) to check out the repo. However, this fails:

$> svn co svn+ssh://svn@svn.kde.org/home/kde/trunk/l10n-support/de/summit
svn: E170013: Konnte nicht mit Projektarchiv bei URL »svn+ssh://svn@svn.kde.org/home/kde/trunk/l10n-support/de/summit« verbinden
svn: E210002: Um Probleme mit der Konfiguration von SSH zu untersuchen, entfernen Sie die Option »-q« von »ssh« im Abschnitt »[tunnels]« Ihrer Konfigurationsdatei für Subversion.
svn: E210002: Netzwerkverbindung wurde unerwartet geschlossen

It seems like I have to upload my public SSH key somewhere to authenticate with the server. But where? I don’t see an option at websvn.kde.org.
So, I looked at the Infrastructure/Subversion wiki page, which says:

Subversion users currently using ssh access should use protocol svn+ssh while subversion users currently using password access should use protocol https […]

But this also leads to an error:

$> svn co svn+https://svn@svn.kde.org/home/kde/trunk/l10n-support/de/summit
svn: E170013: Konnte nicht mit Projektarchiv bei URL »svn+https://svn@svn.kde.org/home/kde/trunk/l10n-support/de/summit« verbinden
svn: E125002: Undefiniertes Tunnelschema »https«

Can somebody help me on how to get started? I am quite familiar with git and its forges (GitLab and GitHub), but not so with SVN…

Among other sites, I searched here for information to no avail:

2

You used svn+https instead of svn+ssh though?

It’s been a while that I don’t translate anything, but I think you need to add it to your Invent account.

Edit: yes, checking some e-mails in the translation mailing list confirmed this.

Edit2: I have edited the wiki to be clear about this, although it’s very outdated in some other respects.

1 Like
3

Yeah, because what I quoted above said something about https access if one doesn’t have a SSH key.

I actually added it to KDE Identity - If I understood correctly, keys you add there will get distributed to all KDE stuff after some time.

Unfortunately, I cannot really tell what the issue was and what solved it for me in the end, but now everything works as expected!