librsync fails with error "job made no progress"

Bug #332009 reported by gcc
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
librsync (Debian)
Unknown
Unknown
librsync (Ubuntu)
Fix Released
Undecided
Unassigned
Declined for Dapper by Michael Terry

Bug Description

As seen with rdiff-backup (which uses librsync) on dapper:

starting backup /usr/local/sbin/backup-by-rdiff at Fri Feb 20 03:00:01 GMT 2009
python: ERROR: (rs_job_iter) internal error: job made no progress [orig_in=1, orig_out=65536, final_in=1, final_out=65536]
UpdateError var/lib/mysql/pmacct/acct_v6.MYD librsync error 107 while in patch cycle

This causes the update of the specified file to fail. This is a well-known bug in librsync. See Debian bug #355178. Debian has released a fixed package. I think they used the patch which was attached on Sourceforge (http://sourceforge.net/tracker/index.php?func=detail&aid=1439412&group_id=56125&atid=479441) and applied to librsync cvs.

Please patch librsync on dapper to match Debian's.

Michael Terry (mterry)
Changed in librsync (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.