Bug#975270: rdiff-backup: Can't talk to the version from buster
Samuel Thibault, le dim. 27 juin 2021 23:06:03 +0200, a ecrit: > Samuel Thibault, le ven. 18 juin 2021 19:27:40 +0200, a ecrit: > > Samuel Thibault, le dim. 16 mai 2021 19:03:11 +0200, a ecrit: > > > Gregor Zattler, le dim. 16 mai 2021 18:50:42 +0200, a ecrit: > > > > * Samuel Thibault [13. Mai. 2021]: > > > > > Kurt Roeckx, le jeu. 19 nov. 2020 20:40:05 +0100, a ecrit: > > > > >> I recently found out that my backup has broken for months. > > > > > > > > > > Not for month, but this does break my backups now that I try to > > > > > upgrade > > > > > some machines, and I don't have another solution than to either > > > > > downgrade the package, or upgrade all my machines at the same time > > > > > (!?) > > > > > to get my backups working again. > > > > > > > > the rdiff-backup project provides a helpful document > > > > regarding this: > > > > > > > > https://github.com/rdiff-backup/rdiff-backup/blob/master/docs/migration.md > > > > > > > > providing this document in the NEWS.Debian file might be > > > > enough in order to close this bug? > > > > > > Perhaps we could have a buster-backports package, so that before > > > upgrading machines to bullseye, we first just upgrade rdiff-backup on > > > all buster machines? > > > > I have uploaded it to buster-backports, it's now in so people can > > pre-upgrade. I'd however probably still be important to ship a > > NEWS.Debian entry to let people about about the incompatibility issue. > > I have uploaded so, and requested an unblock. (filed as Bug#990379)
Bug#975270: rdiff-backup: Can't talk to the version from buster
Samuel Thibault, le ven. 18 juin 2021 19:27:40 +0200, a ecrit: > Samuel Thibault, le dim. 16 mai 2021 19:03:11 +0200, a ecrit: > > Gregor Zattler, le dim. 16 mai 2021 18:50:42 +0200, a ecrit: > > > * Samuel Thibault [13. Mai. 2021]: > > > > Kurt Roeckx, le jeu. 19 nov. 2020 20:40:05 +0100, a ecrit: > > > >> I recently found out that my backup has broken for months. > > > > > > > > Not for month, but this does break my backups now that I try to upgrade > > > > some machines, and I don't have another solution than to either > > > > downgrade the package, or upgrade all my machines at the same time (!?) > > > > to get my backups working again. > > > > > > the rdiff-backup project provides a helpful document > > > regarding this: > > > > > > https://github.com/rdiff-backup/rdiff-backup/blob/master/docs/migration.md > > > > > > providing this document in the NEWS.Debian file might be > > > enough in order to close this bug? > > > > Perhaps we could have a buster-backports package, so that before > > upgrading machines to bullseye, we first just upgrade rdiff-backup on > > all buster machines? > > I have uploaded it to buster-backports, it's now in so people can > pre-upgrade. I'd however probably still be important to ship a > NEWS.Debian entry to let people about about the incompatibility issue. I have uploaded so, and requested an unblock. Samuel
Bug#975270: rdiff-backup: Can't talk to the version from buster
Hello, Samuel Thibault, le dim. 16 mai 2021 19:03:11 +0200, a ecrit: > Gregor Zattler, le dim. 16 mai 2021 18:50:42 +0200, a ecrit: > > * Samuel Thibault [13. Mai. 2021]: > > > Kurt Roeckx, le jeu. 19 nov. 2020 20:40:05 +0100, a ecrit: > > >> I recently found out that my backup has broken for months. > > > > > > Not for month, but this does break my backups now that I try to upgrade > > > some machines, and I don't have another solution than to either > > > downgrade the package, or upgrade all my machines at the same time (!?) > > > to get my backups working again. > > > > the rdiff-backup project provides a helpful document > > regarding this: > > > > https://github.com/rdiff-backup/rdiff-backup/blob/master/docs/migration.md > > > > providing this document in the NEWS.Debian file might be > > enough in order to close this bug? > > Perhaps we could have a buster-backports package, so that before > upgrading machines to bullseye, we first just upgrade rdiff-backup on > all buster machines? I have uploaded it to buster-backports, it's now in so people can pre-upgrade. I'd however probably still be important to ship a NEWS.Debian entry to let people about about the incompatibility issue. Samuel
Bug#975270: rdiff-backup: Can't talk to the version from buster
Hello, Samuel Thibault, le dim. 16 mai 2021 19:03:11 +0200, a ecrit: > Gregor Zattler, le dim. 16 mai 2021 18:50:42 +0200, a ecrit: > > * Samuel Thibault [13. Mai. 2021]: > > > Kurt Roeckx, le jeu. 19 nov. 2020 20:40:05 +0100, a ecrit: > > >> I recently found out that my backup has broken for months. > > > > > > Not for month, but this does break my backups now that I try to upgrade > > > some machines, and I don't have another solution than to either > > > downgrade the package, or upgrade all my machines at the same time (!?) > > > to get my backups working again. > > > > the rdiff-backup project provides a helpful document > > regarding this: > > > > https://github.com/rdiff-backup/rdiff-backup/blob/master/docs/migration.md > > > > providing this document in the NEWS.Debian file might be > > enough in order to close this bug? > > Perhaps we could have a buster-backports package, so that before > upgrading machines to bullseye, we first just upgrade rdiff-backup on > all buster machines? So, does this sound like a possibility? (rdiff-backup is marked for auto-removal on june 15th) Samuel
Bug#975270: rdiff-backup: Can't talk to the version from buster
Hello, Gregor Zattler, le dim. 16 mai 2021 18:50:42 +0200, a ecrit: > * Samuel Thibault [13. Mai. 2021]: > > Kurt Roeckx, le jeu. 19 nov. 2020 20:40:05 +0100, a ecrit: > >> I recently found out that my backup has broken for months. > > > > Not for month, but this does break my backups now that I try to upgrade > > some machines, and I don't have another solution than to either > > downgrade the package, or upgrade all my machines at the same time (!?) > > to get my backups working again. > > the rdiff-backup project provides a helpful document > regarding this: > > https://github.com/rdiff-backup/rdiff-backup/blob/master/docs/migration.md > > providing this document in the NEWS.Debian file might be > enough in order to close this bug? Perhaps we could have a buster-backports package, so that before upgrading machines to bullseye, we first just upgrade rdiff-backup on all buster machines? Samuel
Bug#975270: rdiff-backup: Can't talk to the version from buster
Hi Samuel, debian developers, * Samuel Thibault [13. Mai. 2021]: > Control: severity -1 serious > > Kurt Roeckx, le jeu. 19 nov. 2020 20:40:05 +0100, a ecrit: >> I recently found out that my backup has broken for months. > > Not for month, but this does break my backups now that I try to upgrade > some machines, and I don't have another solution than to either > downgrade the package, or upgrade all my machines at the same time (!?) > to get my backups working again. the rdiff-backup project provides a helpful document regarding this: https://github.com/rdiff-backup/rdiff-backup/blob/master/docs/migration.md providing this document in the NEWS.Debian file might be enough in order to close this bug? Ciao; Gregor
Bug#975270: rdiff-backup: Can't talk to the version from buster
Control: severity -1 serious Hello, Kurt Roeckx, le jeu. 19 nov. 2020 20:40:05 +0100, a ecrit: > I recently found out that my backup has broken for months. Not for month, but this does break my backups now that I try to upgrade some machines, and I don't have another solution than to either downgrade the package, or upgrade all my machines at the same time (!?) to get my backups working again. > Couldn't start up the remote connection by executing > > ssh -C X rdiff-backup --server Currently it rather says Fatal: rdiff-backup does not have the same version at the source and at the destination. Which is more informative, but still pose the same concern. Samuel
Bug#975270: rdiff-backup: Can't talk to the version from buster
Package: rdiff-backup Version: 2.0.5-1 Severity: important Hi, I recently found out that my backup has broken for months. It seems that the version from testing doesn't want to talk to the version from stable/buster. It gives the following error: Exception 'object.__new__(X): X is not a type object (classobj)' raised of class '': File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 304, in error_check_Main try: Main(arglist) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 324, in Main take_action(rps) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 278, in take_action connection.PipeConnection(sys.stdin, sys.stdout).Server() File "/usr/lib/python2.7/dist-packages/rdiff_backup/connection.py", line 355, in Server self.get_response(-1) File "/usr/lib/python2.7/dist-packages/rdiff_backup/connection.py", line 315, in get_response try: req_num, object = self._get() File "/usr/lib/python2.7/dist-packages/rdiff_backup/connection.py", line 241, in _get if format_string == "o": result = cPickle.loads(data) File "/usr/lib/python2.7/copy_reg.py", line 48, in _reconstructor obj = object.__new__(cls) Traceback (most recent call last): File "/usr/bin/rdiff-backup", line 30, in rdiff_backup.Main.error_check_Main(sys.argv[1:]) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 304, in error_check_Main try: Main(arglist) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 324, in Main take_action(rps) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 278, in take_action connection.PipeConnection(sys.stdin, sys.stdout).Server() File "/usr/lib/python2.7/dist-packages/rdiff_backup/connection.py", line 355, in Server self.get_response(-1) File "/usr/lib/python2.7/dist-packages/rdiff_backup/connection.py", line 315, in get_response try: req_num, object = self._get() File "/usr/lib/python2.7/dist-packages/rdiff_backup/connection.py", line 241, in _get if format_string == "o": result = cPickle.loads(data) File "/usr/lib/python2.7/copy_reg.py", line 48, in _reconstructor obj = object.__new__(cls) TypeError: object.__new__(X): X is not a type object (classobj) Fatal Error: Truncated header string (problem probably originated remotely) Couldn't start up the remote connection by executing ssh -C X 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 (2.0.5). If I downgrade to the local version 1.2.8-7, which is also the remote version, things work. Kurt
