blob: 742d22e2dcde1f6395ed4278670a73b45d197839 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
|
[[!comment format=mdwn
username="https://launchpad.net/~eythian"
nickname="eythian"
subject="comment 5"
date="2013-07-12T10:43:23Z"
content="""
Good thing I set up obnam a while ago :)
Anyway, yes, a very similar pattern of corruption can be seen here. It might be worth nothing that it starts in a different place in the file. The one I'm looking at now begins at byte 0x1C, whereas it was a little bit further into the file previously.
I created a large file that'd make the issue really clear and synced it over, and of course, everything worked perfectly.
Here is a pair of small files that shows the problem, from around the 0x4BC mark.
<http://www.kallisti.net.nz/~robin/good-bad-annex-files.tar.gz>
"""]]
|
