Hello Folks, just for your information. The rsync package in Ubuntu 22.04 LTS was updated from 3.2.3 to 3.2.7. This triggers the known and still fixed rsync-incompatibility bug [1] in Back In Time because BIT in Ubuntu 22.04 LTS still is quit old and not able to handle the "new argument protection" introduced with rsync 3.2.4. It seems that rsync itself doesn't follow Semantic Versioning. It was a big change of behavior and should have been a minor update (Version number 3.3 instead of 3.2.4). On the other site the Ubuntu folks should have read the changelog more carefully. At the end currently BIT is "broken" [2] in Ubuntu 22.04. The solution is to use BIT from upstream repo or PPA. Or using the workaround described in the bug [1]. I opened a question about update policy at Ubuntu rsync [3] and also informed the rsync upstream maintainer about the situation. Kind Christian [1] -- <https://github.com/bit-team/backintime/issues/1247> [2] -- <https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2009756> [3] -- <https://answers.launchpad.net/ubuntu/+source/rsync/+question/705772>
I do realize that I mixed up my understanding of a "stable" GNU/Linux version (e.g. Debian stable) and a "Long Term Support" (LTS) release.
Ubuntu 22.04 LTS has just received an update to a patched version of BackInTime 1.2.1. The changelog is here: https://changelogs.ubuntu.com/changelogs/pool/universe/b/backintime/backinti... Quote: backintime (1.2.1-3ubuntu0.3) jammy-security; urgency=medium * Fix compatibility with rsync security update (LP: #2009756) - debian/patches/rsync_compat.patch: fix changes to argument protection in common/config.py, common/snapshots.py, common/sshtools.py, common/test/test_sshtools.py, common/test/test_takeSnapshot.py, common/tools.py. -- Marc Deslauriers <marc.deslauriers@ubuntu.com> Thu, 09 Mar 2023 08:02:57 -0500 Cheers, Michael On 09.03.2023 11:12, c.buhtz@posteo.jp wrote:
Hello Folks,
just for your information.
The rsync package in Ubuntu 22.04 LTS was updated from 3.2.3 to 3.2.7.
This triggers the known and still fixed rsync-incompatibility bug [1] in Back In Time because BIT in Ubuntu 22.04 LTS still is quit old and not able to handle the "new argument protection" introduced with rsync 3.2.4.
It seems that rsync itself doesn't follow Semantic Versioning. It was a big change of behavior and should have been a minor update (Version number 3.3 instead of 3.2.4). On the other site the Ubuntu folks should have read the changelog more carefully.
At the end currently BIT is "broken" [2] in Ubuntu 22.04. The solution is to use BIT from upstream repo or PPA. Or using the workaround described in the bug [1].
I opened a question about update policy at Ubuntu rsync [3] and also informed the rsync upstream maintainer about the situation.
Kind Christian
[1] -- <https://github.com/bit-team/backintime/issues/1247> [2] -- <https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2009756> [3] -- <https://answers.launchpad.net/ubuntu/+source/rsync/+question/705772> _______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-leave@python.org https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: foss@michael-bueker.de
participants (2)
-
c.buhtz@posteo.jp
-
Michael Büker