Re: Version Woes

[Brian Bouterse]

Thanks Frank and Patrik. I did get my Debian system upgraded using the pypi
installation method and my backup worked!

@Patrik your notes helped me, but I did things slightly differently. This
was on Debian stretch. I really should upgrade to Buster but it's a remote
machine and ... COVID.

Also the curl and run the python script to install pip method is pretty
official, but it's kind of scary. Instead I used the pip3 package with:
sudo apt install python3-pip
After that I could run `pip3 freeze` for example, to confirm it works

Instead of virtualenv I used venv which for python3 I believe is preferred
(I think virtualenv is deprecated). To get that installed and the venv
created I did this:
sudo apt-get install python3-venv
sudo python3 -m venv /opt/rdiff-backup2

I did need apt install libacl1-dev, but on my system I also needed
librsync-dev so I installed those along with Python3 dev using
sudo apt install python3-dev libacl1-dev librsync-dev
Without librsync-dev rdiff-backup wouldn't compile, and without
libacl1-dev, pylibacl wouldn't compile.

At that point this command did work:
sudo /opt/rdiff-backup2/bin/pip3 install rdiff-backup pyxattr pylibacl but
it couldn't build the wheel, it gave this error:

```
sudo /opt/rdiff-backup2/bin/pip3 install rdiff-backup
Collecting rdiff-backup
  Using cached
https://files.pythonhosted.org/packages/af/61/4edbe10fbee6e2490207314ac9c036e7135784a328629079860bfecc29ea/rdiff-backup-2.0.0.tar.gz
Building wheels for collected packages: rdiff-backup
  Running setup.py bdist_wheel for rdiff-backup ... error
  Complete output from command /opt/rdiff-backup2/bin/python3 -u -c "import
setuptools,
tokenize;__file__='/tmp/pip-build-gex_7lx1/rdiff-backup/setup.py';f=getattr(tokenize,
'open', open)(__file__);code=f.read().replace('\r\n',
'\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d
/tmp/tmpz1_uun1spip-wheel- --python-tag cp35:
  usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
     or: -c --help [cmd1 cmd2 ...]
     or: -c --help-commands
     or: -c cmd --help

  error: invalid command 'bdist_wheel'

  ----------------------------------------
  Failed building wheel for rdiff-backup
  Running setup.py clean for rdiff-backup
Failed to build rdiff-backup
Installing collected packages: rdiff-backup
  Running setup.py install for rdiff-backup ... done
Successfully installed rdiff-backup-2.0.0
```

That was resolved with `/opt/rdiff-backup2/bin/pip3 install wheel`. After
that the following command completed with no errors:

```
sudo /opt/rdiff-backup2/bin/pip3 install rdiff-backup pyxattr pylibacl
Collecting rdiff-backup
  Using cached
https://files.pythonhosted.org/packages/af/61/4edbe10fbee6e2490207314ac9c036e7135784a328629079860bfecc29ea/rdiff-backup-2.0.0.tar.gz
Collecting pyxattr
  Using cached
https://www.piwheels.org/simple/pyxattr/pyxattr-0.7.1-cp35-cp35m-linux_armv7l.whl
Collecting pylibacl
  Using cached
https://files.pythonhosted.org/packages/b5/46/9438665705fbd76015ee2cdda2c136364504272de08124b73ffb3f5cf1a5/pylibacl-0.5.4.tar.gz
Building wheels for collected packages: rdiff-backup, pylibacl
  Running setup.py bdist_wheel for rdiff-backup ... done
  Stored in directory:
/root/.cache/pip/wheels/4d/71/ee/13c25188b5639e34ad22a811fabe1cfcfeac56ba334d120729
  Running setup.py bdist_wheel for pylibacl ... done
  Stored in directory:
/root/.cache/pip/wheels/66/4e/0d/804daa57f0f46ce432e9d050ed0ec8521ce2113c00174104c8
Successfully built rdiff-backup pylibacl
Installing collected packages: rdiff-backup, pyxattr, pylibacl
Successfully installed pylibacl-0.5.4 pyxattr-0.7.1 rdiff-backup-2.0.0
```

Your symlink instructions to put it onto my path worked and my local 1.9.0
client (Fedora) successfully backed up my pypi based Debian install (2.0.0).

Do you want any of this sent to you as a PR to your guide? Or maybe the
centos instructions too? What repo and branch is the best to open the PR
against? Also what version formally because the Python3 version?

Thanks again!
Brian



On Thu, Apr 16, 2020 at 7:08 AM Frank Crawford <address@hidden>
wrote:

> Brian,
>
> FYI, the incompatibility is really between python2 and python3 versions,
> so, 1.9.X and 2.0.0 are interoperable.
>
> Regards
> Frank
>
> On Wed, 2020-04-15 at 18:52 -0400, Brian Bouterse wrote:
>
> I understand how maintaining the protocol compatibility wasn't an option.
>
> It's actually pretty great the on-disk layout is backwards compatible. Your
>
> guide looks pretty good. I have a few questions.
>
>
> In my case it's the section at the bottom "Use Case: Remote to Local
>
> (push)". My local is the 1.9.0b1 (Fedora) machine as my remote is the 1.2.8
>
> (Debian) machine. What do you think the right process would be for me to
>
> try? If it works for me I could send some docs back to your PR.
>
>
> Is my first step to upgrade the remote Debian machine from 1.2.8 -> 2.0.0?
>
> Can I use the "On Debian" portion of guide to upgrade that 2.0.0?
>
>
> What version was the backwards compatible protocol version made? Is the
>
> 1.9.0 client the new or the old protocol?
>
>
> Any other advice on the process I should try in my case?
>
>
> Thanks for any info you can provide.
>
>
> -Brian
>
>
>
>
> On Tue, Apr 14, 2020 at 9:04 PM Patrik Dufresne <
>
> address@hidden
>
> > wrote:
>
>
> Hello Brian,
>
>
> We are aware of the incompatibles between the legacy version and the new
>
> version. It's was not possible in a reasonable amount of time to keep it
>
> backwards compatible.
>
>
> I'm currently working on a migration guide. It's a work in progress...
>
>
> Check this out and let me know what you think
>
>
>
> https://github.com/rdiff-backup/rdiff-backup/blob/ikus-migration-docs/docs/migration.md
>
>
>
>
> On Tue., Apr. 14, 2020, 5:26 p.m. Brian Bouterse, <
>
> address@hidden
>
> >
>
> wrote:
>
>
> I use rdiff-backup and love it, but I'm challenged by what I think is a
>
> version mismatch issue.
>
>
> My central rdiff-backup server has version 1.9.1b0. Now I need to backup a
>
> Debian system and this system and even the latest (
>
> https://packages.debian.org/buster/rdiff-backup
>
>  ) uses 1.2.8-7.
>
>
> When I attempt to run the test command:   `rdiff-backup --test-server
>
> example.com::/ignore` I get the error:
>
>
> Couldn't start up the remote connection by executing
>
>
>     ssh -C example.com rdiff-backup --server
>
>
> Remember that, under the default settings, rdiff-backup must be
>
> installed in the PATH on the remote system.  See the man page for more
>
> information on this.  This message may also be displayed if the remote
>
> version of rdiff-backup is quite different from the local version
>
> (1.9.1b0).
>
>
> When I do manually run `ssh -C example.com
>
> <
>
> address@hidden
>
> > rdiff-backup --server` it does launch
>
> the server and manual ssh and run rdiff-backup does show it's on the path.
>
> So I've concluded I have a version mismatch.
>
>
> Do you agree that is my issue?
>
>
> So I went to manually install it, but the downloads page takes me to
>
> https://github.com/rdiff-backup/rdiff-backup/releases
>
>  which shows a 10
>
> year
>
> gap and there isn't a version < 2.0 that I can see there.
>
>
> How do I install a version like 1.9.1b0 on Debian?
>
>
> Thank you!
>
> Brian
>
>
>
> --
>
> Brian Bouterse
>
>
>
>
>

-- 
Brian Bouterse