Access to SVN will be closed soon!
… but only if you are not yet using an ssh based svn account!
According to the schedule, we will stop providing access to svn if you use a password based account on August 25th.
If you have not converted yet. Do it now. Though everyone affected should have received a personal invitation already. Don’t wait any longer, do it now! If you did not contact sysadmin now!
You might wonder how many accounts are affected. When we started with the first round of invitations two or three months ago, we sent out 1209 invitation to convert. This time we have sent 861 invitation. That means 350 contributors already converted [edit: or indicated the account can be deleted because it is no longer used]
Eike Hein did a further analysis of those 861 accounts that are not yet git-ready. He noted that only 92 accounts of those have been active this year, only 56 with more than 10 commits this year. That means we are on track with the conversion, and we are confident that those accounts will be converted in this round of invitations.
One of the reasons is that ssh only worked on port 22, some people are behind a firewall, and have only access to port 80 (http) and 443 (https). Starting from today we also offer svn via ssh on port 443. That means those account holders can convert too now.
Hi,
I’m one of those 861 accounts who are not converted yet (and even in the 92 ones with some activity this year). The reason is not only the firewall, but also the proxy I’m behind at work.
When I type “svn ls svn+ssh://svn.kde.org/home/kde/…” I get an unknown host error message, although the proxy settings are correctly configured (it works with svn://...). Is there documentation somewhere how to make svn+ssh work through a proxy?
You might want to consider allowing a “CONNECT localhost:22″ on that port if it’s serving HTTPS as well at the same time (using “sslh”).
I think there are firewalls out there inspecting for proper SSL handshakes – the SSH banner is trivial to detect.
Yes, we have documentation for accessing on port 443. That’s exactly what i described in my blog for when you are behind a firewall.
You will get the documentation automatically when you convert.
We don’t use that.
Hoi Tom,
thanx for the ping… I had not seen that invite, but will now get my account converted…
And, thanx for the push to make some more commits :) I guess I should do some work on the Strigi-Chemistry project then :)
Egon
Tom,
it seems my email address associated with my SVN account is outdated… I am not getting any email… who should I contact?
My account is ‘egonw’:
http://websvn.kde.org/trunk/playground/utils/kfile-chemical/src/cml/kfile_cml.cpp?revision=503269&view=markup
Egon
Hi Egon, please contact sysadmin at https://bugs.kde.org/enter_sysadmin_request.cgi
Hi Tom, with the help from Ben I updated the accounts file, which allowed me to get that email sent.
Now, that email only mentions that I need to send a SSH key… I always used svn+ssh://… so nothing really seems to have changed for me… there is nothing that indicates how to get a Git account, or that Subversion will be dropped…
Is this “conversion” just about getting everyone to submit a SSH key then?
Every ssh based svn account automatically has access to the git repository. But every passwd based svn account has not, hence those have to convert their account. Not you, you are fine :)