#16 --verify fails on multiple full backups

[rob adair]

--verify succeeds only on the most recent version of the full backup. The md5sum check fails because the filenames in the older .check files are not updated properly when the full backup versions are renamed. The filenames in the .check file are prepended by ./ while the sed command in backup2l looks for a leading space. Changed the sed command in backup2l to 'sed "s/ \.\/$VOLNAME.$SRC/ \.\/$VOLNAME.$DST/"' to fix the problem.

[Amedee Van Gasse]

I can confirm this bug.
I purged a few full backups which resulted in renaming of subsequent backups.
The associated .check files did not get updated accordingly.

Can somebody please make a patch file for this bugfix so that I can test it?
"The filenames in the .check file are prepended by ./ while the sed command in backup2l looks for a leading space. Changed the sed command in backup2l to 'sed "s/ \.\/$VOLNAME.$SRC/ \.\/$VOLNAME.$DST/"' to fix the problem."
Thanks.

[Amedee Van Gasse]

Example of a check file when I had 8 full backups and purged full backup 1-7, which renamed full backup 8 to 1:

8f1cd08f7474507751b24d78368f9b32 ./all.801.skipped.gz
5a9c87c7ebba4801c0252b2634d1b33a ./all.801.obsolete.gz
209847ac7775ed5ee54ae714954f2729 ./all.801.list.gz
b1403dd30da8afb4871690aca2c7327e ./all.801.tar.lz
37c91e1872728d15d774fe5778f252a2 ./all.801.new.gz
4b4870721fb61a51a22708520f9a72ba ./all.801.error.gz
88a854a773fe98088ac20fc46058df0d all.1.list.gz

As you can see, 801 did not get renamed to 101.