|
From: | Robert Nichols |
Subject: | Re: Version Woes |
Date: | Fri, 17 Apr 2020 21:48:43 -0500 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 |
On 4/17/20 8:46 PM, Frank Crawford wrote:
On Fri, 2020-04-17 at 08:27 -0500, Robert Nichols wrote:On 4/17/20 12:52 AM, address@hidden wrote: That's if you _can_ upgrade on both sides. I have CentOS 6 clients, and their Python 3 version is 3.4.10, which is too old for rdiff-backup 2.0. The CentOS 8 server has to support both 1.2 and 2.0 clients, regardless of what needs to be done to accomplish that.Do you actually have a version of 1.2 that runs on CentOS 8?
It just takes a couple of symlinks to make rdiff-backup-1.2.8-6 work with the python2-2.7.16.12 that is available for CentOS 8. ln -s python2.7 /usr/lib64/python-2.6 ln -s libpython2.7.so.1.0 /usr/lib64/libpython2.6.so.1.0 The /usr/bin/rdiff-backup script needs to invoke /usr/bin/python2 explicitly. I haven't tested it fully, but the basic operations seem to work. I could probably rebuild rdiff-backup-1.2.8-6 to use python2.7 directly. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it.
[Prev in Thread] | Current Thread | [Next in Thread] |