From users-return-28868-archive-asf-public=cust-asf.ponee.io@subversion.apache.org Mon Oct 5 09:18:58 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mailroute1-lw-us.apache.org (mailroute1-lw-us.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with ESMTPS id C2DFA18037A for ; Mon, 5 Oct 2020 11:18:58 +0200 (CEST) Received: from mail.apache.org (localhost [127.0.0.1]) by mailroute1-lw-us.apache.org (ASF Mail Server at mailroute1-lw-us.apache.org) with SMTP id 00B6B121FA9 for ; Mon, 5 Oct 2020 09:18:57 +0000 (UTC) Received: (qmail 68440 invoked by uid 500); 5 Oct 2020 09:18:57 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 68425 invoked by uid 99); 5 Oct 2020 09:18:57 -0000 Received: from spamproc1-he-de.apache.org (HELO spamproc1-he-de.apache.org) (116.203.196.100) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2020 09:18:57 +0000 Received: from localhost (localhost [127.0.0.1]) by spamproc1-he-de.apache.org (ASF Mail Server at spamproc1-he-de.apache.org) with ESMTP id 61FE51FF39B for ; Mon, 5 Oct 2020 09:18:56 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamproc1-he-de.apache.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.2, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamproc1-he-de.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=visualsvn.com Received: from mx1-he-de.apache.org ([116.203.227.195]) by localhost (spamproc1-he-de.apache.org [116.203.196.100]) (amavisd-new, port 10024) with ESMTP id qVYrNi16xIVG for ; Mon, 5 Oct 2020 09:18:55 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2607:f8b0:4864:20::f30; helo=mail-qv1-xf30.google.com; envelope-from=pavel.lyalyakin@visualsvn.com; receiver= Received: from mail-qv1-xf30.google.com (mail-qv1-xf30.google.com [IPv6:2607:f8b0:4864:20::f30]) by mx1-he-de.apache.org (ASF Mail Server at mx1-he-de.apache.org) with ESMTPS id 977397FB7B for ; Mon, 5 Oct 2020 09:18:55 +0000 (UTC) Received: by mail-qv1-xf30.google.com with SMTP id 13so2688600qvc.9 for ; Mon, 05 Oct 2020 02:18:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=visualsvn.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DpuNkBAjNNFQj9PH686Yp8jLA1loJVOUar6IeBE4zn0=; b=P2m0Oo3fwHKiMhrDCPi1xOXYIpOSZBj+PQ71bk7rnUDfgFgkwEhk2NT6JpTSBWKnpL nsdijo3ypAOn4/eI/8i2EFFCvWF5K2w9pH6EmvqvYFQqrAZZ9JlmSctaA+GqEYyuL106 7TtCga0Tcl9ITCxBEOPsr6uOOhAhLvhOPO92U= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DpuNkBAjNNFQj9PH686Yp8jLA1loJVOUar6IeBE4zn0=; b=jMIRq6i+LZ5IAtkB9UeEiXZlaere/Dp6DjHuTj7YUNSPVuVUxQboXSfLxpz95s2zbm E4XFutlwTxcWZv45ITH66TKxtho/8p6h9lg2Ee/g+R2mV3FBe8cRnYJubS2CuQwm1luX hNINbw/1TdyimlnbEn4hLBlhy4zhJbkbFqbTmaISyIYf2u9IqYmUE/BYD6Wkvb0Z3bqH bXKokRTjeogsieEFfaXhSOl7MKslzDgA0KPTt7Q/tP8p2Pp2a3uKA4HOLfqLO9f+MXGQ F44s1xn6o18vQ436Hfm0R3MfXOxoW6Ett7rrmj327CK2G6AXq1z+lo6sfOnidJdtwCoF h/yg== X-Gm-Message-State: AOAM531HH/P0RuCx5TTgYdDbdD9SfkkYZhZy6XcjckhCiiQlBvHOQPJO lfN0pcYPGdiX8sL3uXvWOp+4CbT0XNfNR9TYCtgemw== X-Google-Smtp-Source: ABdhPJyv5/s9OvZHTohxzqBDyL0rrTWxJ7/B3ZaS/pEVijH+sXCK2nY4fSuxANTALJGwi8yWPlTChl0P5UOa3Q0Q7Wo= X-Received: by 2002:a0c:f843:: with SMTP id g3mr13701998qvo.1.1601889527662; Mon, 05 Oct 2020 02:18:47 -0700 (PDT) MIME-Version: 1.0 References: <6ihenf9kqonfobkv5hlrurupr91r0098b6@4ax.com> In-Reply-To: <6ihenf9kqonfobkv5hlrurupr91r0098b6@4ax.com> From: Pavel Lyalyakin Date: Mon, 5 Oct 2020 12:18:12 +0300 Message-ID: Subject: Re: Upgrading visual svn server from 3.7.0 using svn 1.9.7 - how? To: bo.berglund@gmail.com Cc: users@subversion.apache.org Content-Type: multipart/alternative; boundary="00000000000044224805b0e8f84e" --00000000000044224805b0e8f84e Content-Type: text/plain; charset="UTF-8" Hello, On Fri, Oct 2, 2020 at 7:24 PM Bo Berglund wrote: > We are using this setup: > - Main server is running on Windows Server 16 Standard using VisualSVN > version 3.7.0, which apparently uses svn 1.9.7 > Usually you just need to download and run the VisualSVN Server installer to upgrade the server. Please, read the article KB161: Upgrading to VisualSVN Server 4.2 before beginning the upgrade. The article includes pre- and post- upgrade checklists to ensure smooth upgrade. > - The server is using svnsync nightly to synchronize over the Internet > to a mirror SVN server version 1.9.7 running on Ubuntu 18.04 Server on > a different location entirely. > No user operations are allowed on the mirror, it is just a backup. > > My problem is this: > The VisualSVN server is seriously out of date and needs to be > upgraded. In its own management console it suggests upgrading to 4.2.2 > but does not say which version of svn will then be running. > In fact it seems like they are intentionally hiding the svn version in > their web pages.. :( > > And I suspect that there might be problems concerning the svnsync > commands if the backup mirror server is not upgraded to the same svn > version, right? > > But how do I do that on Ubuntu when I cannot find out which svn > version they use? > > Or does it not matter, i.e. can the main and mirror servers be using > different svn versions? > > -- > Bo Berglund > Developer in Sweden > -- With best regards, Pavel Lyalyakin VisualSVN Team --00000000000044224805b0e8f84e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

On Fri, Oct 2, 2020 at 7:24 PM Bo Berglund <bo.berglund@gmail.com> wrote:
We are usin= g this setup:
- Main server is running on Windows Server 16 Standard using VisualSVN
version 3.7.0, which apparently uses svn 1.9.7

Usually you just need to download and run the VisualSVN Server install= er to upgrade the server. Please, read the article KB161: Upgrading to VisualSVN Server 4.2= before beginning the upgrade. The article includes pre- and post- upgr= ade checklists to ensure smooth upgrade.
=C2=A0
- The server is using svnsync nightly to synchronize over the Internet
to a mirror SVN server version 1.9.7 running on Ubuntu 18.04 Server on
a different location entirely.
No user operations are allowed on the mirror, it is just a backup.
=C2=A0
My problem is this:
The VisualSVN server is seriously out of date and needs to be
upgraded. In its own management console it suggests upgrading to 4.2.2
but does not say which version of svn will then be running.
In fact it seems like they are intentionally hiding the svn version in
their web pages.. :(

And I suspect that there might be problems concerning the svnsync
commands if the backup mirror server is not upgraded to the same svn
version, right?
=C2=A0
But how do I do that on Ubuntu when I cannot find out which svn
version they use?

Or does it not matter, i.e. can the main and mirror servers be using
different svn versions?

--
Bo Berglund
Developer in Sweden

--
With best regards,
Pavel Lyalyakin
VisualSVN Team
--00000000000044224805b0e8f84e--