What does the upgrade path look like from if folks are currently creating
backups using 1.x and they suddenly switch to 2.x? Is there an upgrade
path? Is there a way in EPEL to allow for both versions to exist to ease
migration? i.e. maybe by creating rdiff-backup2 which
supercedes rdiff-backup.
Ideally, it would be nice to have some kind of an upgrade path so we don't
end up breaking all of our backups.
Thanks-
On Mon, Apr 20, 2020 at 6:33 AM Frank Crawford <frank(a)crawford.emu.id.au>
wrote:
We have pushed into testing and intend to eventually release a new
version
of rdiff-backup which has a significant incompatibly with the current
distributed version, when used in client-server mode.
The current version is v1.2.8 and written in Python2, while the new
version is v2.0.0 and written in Python3, and the language change breaks
client-server mode, due to incompatible data representations between
Python2 and Python3. In all other respects the two versions are compatible
including the ability to read and write existing backup repositories.
It should be noted that the v1.2.8 was released over 11 years ago and
while a small number of bug fixes have been added by the community, there
has been no co-ordinated work for a number of years, and no further
development will occur on the Python2 version. All future work,
enhancements and bugfixes, including security bugfixes, will be to the
Python3 version.
If it is necessary to stay with the Python2 version, it is recommended
that you exclude rdiff-backup from future updates.
Also, if you are testing the Python3 update in EPEL-7 (and EPEL-8) some of
the dependencies (python3-pyxattr and py3libacl) are also in the testing
repositories.
If you have any questions about the update, please contact me.
Frank Crawford
FAS: frankcrawford
_______________________________________________
epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org
To unsubscribe send an email to epel-devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproj...
--
Lance Albertson
Director
Oregon State University | Open Source Lab