Lennart, see my comment #11. This fix/SRU is for the root cause when making a backup, preventing the data loss in the first place.
But if you are trying to restore a backup affected by the bug (as you are), the traceback you see when restoring is worked-around by a separate fix in duplicity trunk. You still will not be able to correctly restore the file missing its 65k chunk, but duplicity trunk does prevent the restore from bailing out.
Lennart, see my comment #11. This fix/SRU is for the root cause when making a backup, preventing the data loss in the first place.
But if you are trying to restore a backup affected by the bug (as you are), the traceback you see when restoring is worked-around by a separate fix in duplicity trunk. You still will not be able to correctly restore the file missing its 65k chunk, but duplicity trunk does prevent the restore from bailing out.