From users-return-27831-archive-asf-public=cust-asf.ponee.io@subversion.apache.org Wed Feb 27 23:00:57 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 0213F180608 for ; Thu, 28 Feb 2019 00:00:56 +0100 (CET) Received: (qmail 24776 invoked by uid 500); 27 Feb 2019 23:00:55 -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 24766 invoked by uid 99); 27 Feb 2019 23:00:55 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2019 23:00:55 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id CE767C28AD for ; Wed, 27 Feb 2019 23:00:54 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.2 X-Spam-Level: X-Spam-Status: No, score=-0.2 tagged_above=-999 required=6.31 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id BhmcqUocefVC for ; Wed, 27 Feb 2019 23:00:53 +0000 (UTC) Received: from mail-qt1-f194.google.com (mail-qt1-f194.google.com [209.85.160.194]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id E1C1362478 for ; Wed, 27 Feb 2019 23:00:52 +0000 (UTC) Received: by mail-qt1-f194.google.com with SMTP id p25so21385587qtb.3 for ; Wed, 27 Feb 2019 15:00:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=SWCfGQrFJjFYksh86f7sTYxM0puaVvuIiTnbE21uykQ=; b=p4UJSQloinvwd2ec8ul/GnS68h06TAxWTZeFV+NfmUkfu1UUIb1kurqsu5BYQgAWuN mRk8O8IJBNQF2V7SdDE9eIW/aDpMirxbGe+nbX6J8SdMq6zewBPpIsBChjdOBLdyMYi+ x3gtB3/Zzanf9yd8Q1H5Kb0/XLuC+eXWycSXlTPFMIhAesvo26FC4Ai3wbkc02Z3d5IX f/i3BhNBfRX+FxiHKtJE88TQ4nhcd/peCVTCrIqj8hwVzcEIPPVf739PoDcS/eT0RBL8 Knx6JF8Vkv6u0Ph9J1ZXnjLoVItSIJhq+fuR49azUt7y9XYDfsxobk60LTYlcUPVh6yP Rvtg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=SWCfGQrFJjFYksh86f7sTYxM0puaVvuIiTnbE21uykQ=; b=HRAW0f7ftQySAqZ/B/1T3eqnP087GvBYRdRZZU1oOuSzd+4QTeRSYR90wM0ArJeFNv XRx4+62YtYfpPjpmPNE9pvv1RmfYKOmPwM8n9LTZj2ux5NOmwvVJCtQ4SfdLVWzGZ//M 0wDrQJpA53lRzcN0Lz5GjYC7qM+CLCXXlYv5VU7zSq4K15wQDFtA5mfcyph/iY1c5B8L Z9CtljepPmX0AIwT3fo9hipqL/ktqar14ZSaHWYubF/4i8yoN1mpaAftONKRhhJ1n2fg GJxWMMvfa21JX/x6+J3iCMVZUtiKBGvgjys+LDHQSxwA1eyKKh1tS+Y/jd+k3AUE3PmN bW4A== X-Gm-Message-State: APjAAAVd+dQ36LexTzkFLIqtRWq8zjPY83TTJcrVWha0HBefclZZnpGL wT2wYUgrFse2UQ9rO+UNA0kR9omd X-Google-Smtp-Source: APXvYqwoLPAgOi72hz7JowdMwdb4pz2NpuCFpifbk81rj/9jRkSbcJwrrgV6QW3wQAcZDZ8MKzgL/Q== X-Received: by 2002:a0c:98c9:: with SMTP id g9mr3940259qvd.150.1551308452317; Wed, 27 Feb 2019 15:00:52 -0800 (PST) Received: from [192.168.5.59] (196-182.spoffordnh.ArgentCom.net. [199.204.196.182]) by smtp.gmail.com with ESMTPSA id 5sm10430385qtw.69.2019.02.27.15.00.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 27 Feb 2019 15:00:50 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: How to safely upgrade svn on ubuntu 16? From: Mark Phippard X-Mailer: iPad Mail (16E5201e) In-Reply-To: <323e7epdne4414nhclv5e9d41jv6mk8fad@4ax.com> Date: Wed, 27 Feb 2019 18:00:49 -0500 Cc: users@subversion.apache.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <78fc7e9kc188sceje8iapcdnscd3qfoqc8@4ax.com> <323e7epdne4414nhclv5e9d41jv6mk8fad@4ax.com> To: bo.berglund@gmail.com > On Feb 27, 2019, at 5:24 PM, Bo Berglund wrote: >=20 > On Wed, 27 Feb 2019 08:44:25 +0100, Bo Berglund > wrote: >=20 >> I am running svn on Ubuntu 16.04.6 LTS. >> It reports the following: >> $ svn --version >> svn, version 1.9.3 (r1718519) >> compiled Aug 10 2017, 16:59:15 on x86_64-pc-linux-gnu >>=20 >> The Ubuntu machine acts as a backup for a Windows 16 based VisualSvn >> server running at a separate location. >> Backups are performed using nightly svnsync commands via the Internet. >>=20 >> The Ubuntu machine and svn were setup for this purpose about a year >> ago and since then Ubuntu has been kept updated using apt upgrade and >> apt dist-upgrade as adviced on the login screen when I regularly check >> in via PuTTY. >>=20 >> But it seems like svn is not being touched by these operations.... >>=20 >> So what is the advice on what to do in order to at least get to the >> latest 1.9 stable release of svn on this machine? >> It seems like that would be 1.9.10... >>=20 >> Since this is a production backup server I am reluctant to risk >> breaking it, obviously. >=20 > More questions after some extensive googling: >=20 > On terminal (PuTTY) login this headless server machine displays: >=20 > New release '18.04.2 LTS' available. > Run 'do-release-upgrade' to upgrade to it. >=20 > Since the svn I use is from the Xenial repository (for Ubuntu 16.04 > LTS) maybe there will never be a later svn version there? >=20 > If so is it safe to use do-release-upgrade (as suggested on login) to > move from Ubuntu 16.04.6 LTS to 18.04.2 LTS instead in order to switch > to a newer ubuntu update repository and therefore get subversion > upgradeable to later versions? >=20 > Will I risk damaging the svn installation or repository data by doing > so? > Or do I have any other option? Is this a client or a server? If the client then generally it is very safe to do. The only question might b= e if you are using any other SVN clients besides the command line that are u= sing the SVN libraries. Even then it is generally very safe but worth knowin= g more details. If it is a server it is also fairly safe. The main concern would be the Apac= he server version change from the upgrade and whether the Apache conf needed= to be adjusted. Mark