subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bo Berglund <bo.bergl...@gmail.com>
Subject Re: Subversion 1.9.7 server on Windows, advice on setting up svnsync?
Date Mon, 26 Mar 2018 05:21:33 GMT
On Sat, 24 Mar 2018 22:40:55 -0500, Bo Berglund
<bo.berglund@gmail.com> wrote:

Contrary to the previous message I found that the only way I could fix
the connectivity was to publish my backup Ubuntu server on the
Internet as a self-signed Apache service on port 443 on my Internet
router.
So the svnsync command will execute on the master server on Windows
and target the remote https URL.

I have read the svnbook 1.7 on the svnsync usage:
http://svnbook.red-bean.com/en/1.7/svn.reposadmin.maint.html#svn.reposadmin.maint.replication
and I have followed its instructions all along to the end.

So I have configured the target mirror server (Ubuntu 16.04) such that
it is accessible on a domain name via https and I have prepared the
hooks all according to the svnbook. The test repository sits at
revision 0.

When done on Ubuntu I moved over to the source server (Windows Server
2016 in a completely different location).
So on the Windows Server command line I issued the commands from the
svnbook.

First, initialize the sync - but I see errors (privacy data mangled):

E:\>svnsync initialize https://xxx.yyy.com/svn/bosse
https://localserver/svn/bosse --sync-username syncuser --sync-password
zzzzz
Error validating server certificate for 'https://xxx.yyy.com:443':
 - The certificate is not issued by a trusted authority. Use the
   fingerprint to validate the certificate manually!
Certificate information:
 - Hostname: xxx.yyy.com
 - Valid: from Mar 25 00:52:45 2018 GMT until Mar 22 00:52:45 2028 GMT
 - Issuer: xxx.yyy.com, IT, xxxsciences Inc, Jarfalla, Stockholm,
SE(user@somedomain.com)
 - Fingerprint:
1C:84:47:97:89:7E:48:3B:C9:08:C0:F5:65:E8:01:B0:7F:DD:DB:21
(R)eject, accept (t)emporarily or accept (p)ermanently?


I have seen this before when accessing a selfsigned server for the
first time, so I replied p and got this:

svnsync: E170011: Repository moved permanently to
'https://xxx.yyy.com/svn/bosse'


What does this mean? I have *not* requested a move, just to initialize
syncronization of the source localserver to the destination mirror
xxx.yyy.com

Not knowing what to do next I tried the synchronize command:

E:\>svnsync synchronize https://xxx.yyy.com/svn/bosse
https://localserver/svn/bosse
svnsync: E170011: Repository moved permanently to
'https://xxx.yyy.com/svn/bosse'

Apparently something has gone wrong, but what?
And what does "moved permanently" mean?
AFAICT nothing has moved or copied...

If I google the visible error message not a single hit I get is
referring to command svnsync...

-- 
Bo Berglund
Developer in Sweden


Mime
View raw message