I'd still like to see this fixed, but based on Ryan's comment from when
he investigated this I don't think we can do this without a failure
case. I presume most reporters won't want to share their data publicly.
But we need a failure case in order to make progress.
Until we have one, I'm marking this bug as Incomplete, as I think that
sets a more accurate expectation. If someone can provide us with a
failure case, please do so and we can set the bug back to Triaged.
If you don't want to share the failure case publicly but are willing to
share it with a Canonical engineer then we can probably arrange
something around that. Please get in touch.
Alternatively if someone doesn't want to share the failure case at all
but is willing to prepare a patch and drive the SRU then that's fine,
too. We can believe you if you report success during pre-upload testing
and SRU verification and others who are affected can confirm.
** Changed in: rsync (Ubuntu Trusty)
Status: Confirmed => Invalid
** Changed in: rsync (Ubuntu Trusty)
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1384503
Title:
rsync fails on large files with compression
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1384503/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
