Relocating svk mirrors
When I created my svk mirrors I used http to connect to my svn repository. However since then I activated https support on my server. Due to some stupidity on my part (and how hard it is to debug webserver configuration problems) I didn’t get it to work until this week (thanks to the TextDrive support). To relocate a mirror you should just have to do like this:
C:\>svk mirror --list
Path Source
============================================================
//andthennothing http://urltorepository
//typo/mirror svn://leetsoft.com/typo/trunk
C:\>svk mirror --relocate //andthennothing https://urltorepositoryC:\>svk mirror --relocate //andthennothing https://urltorepository
Error validating server certificate for 'https://hostname:443':
<snip />
(R)eject, accept (t)emporarily or accept (p)ermanently? p
Type error in argument 2 of svn_auth_cred_ssl_server_trust_t_accepted_failures_set. Expected _p_apr_uint32_t at C:/Development/svk/lib/SVN/Base.pm line 80, <STDIN> line 1.C:\>svn ls https://urltorepository
Error validating server certificate for 'https://hostname:443':
<snip />
(R)eject, accept (t)emporarily or accept (p)ermanently? p
branches/
trunk/
C:\>svk mirror --relocate //andthennothing https://urltorepository
Authentication realm: <https://hostname:443> realm
Password for 'user':
Committed revision 633.
C:\>svk mirror --list
Path Source
============================================================
//andthennothing https://urltorepository
//typo/mirror svn://leetsoft.com/typo/trunkYay! So I guess there’s some problems with adding a certificate through svk at least on Windows (more specifically svn’s Perl bindings on Windows). But as soon as the certificate is cached (through svn) everything works fine.
I feel so much secure now using https instead of http :-)
Update: To relocate a svn checkout you just type svn switch https://urltorepository. Easy peasy!
Zero comments