[Touch-packages] [Bug 1751489] Re: rsync dies with "inflate returned -3 (0 bytes)"

2020-07-03 Thread Bug Watch Updater
** Changed in: rsync (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1751489 Title: rsync dies with "inflate returned -3 (0

[Touch-packages] [Bug 1751489] Re: rsync dies with "inflate returned -3 (0 bytes)"

2019-07-10 Thread Andreas Hasenack
The other hint in the debian bug is that with rsync 3.1.1 (upgraded from 3.1.0) it works. In this bug, 3.1.1 was at the receiving side, and 3.1.0 is the sender. One of the changes in 3.1.1 is a new compression stryle, triggered by -zz. A test to see if this gets rid of the problem, since the

[Touch-packages] [Bug 1751489] Re: rsync dies with "inflate returned -3 (0 bytes)"

2019-01-09 Thread Andreas Hasenack
That bug report also has a comment saying that with --block-size=65536 it worked, but that was for an error code of -5, not -3. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu.

[Touch-packages] [Bug 1751489] Re: rsync dies with "inflate returned -3 (0 bytes)"

2018-06-27 Thread Bug Watch Updater
** Changed in: rsync (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1751489 Title: rsync dies with "inflate returned -3 (0 bytes)"

[Touch-packages] [Bug 1751489] Re: rsync dies with "inflate returned -3 (0 bytes)"

2018-06-27 Thread  Christian Ehrhardt 
Can be avoided not using -z AFAIK it is an issue with compression on very huge files. Theree are similar discussions on e.g. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741628 ** Bug watch added: Debian Bug tracker #741628 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741628 **