On 22.02.2018 21:30, Myria wrote: > When we try to commit a very specific version of a very specific > binary file, we get a SHA-1 collision error from the Subversion > repository: > > D:\confidential>svn commit secret.bin -m "Testing broken commit" > Sending secret.bin > Transmitting file data .svn: E160000: Commit failed (details follow): > svn: E160000: SHA1 of reps '604440 34 134255 136680 > c9f4fabc4d093612fece03c339401058 > db11617ef1454332336e00abc311d44bc698f3b3 605556-czmh/_8' and '-1 0 > 134255 136680 c9f4fabc4d093612fece03c339401058 > db11617ef1454332336e00abc311d44bc698f3b3 605556-czmh/_8' matches > (db11617ef1454332336e00abc311d44bc698f3b3) but contents differ > > > What can cause this?
The simplest explanation would be a corruption of the existing representation on disk. Note that both the MD5 and the SHA1 checksums appear to match, as do the sizes; which makes it even more likely that it's the same file but the copy in the repository is somehow corrupted. -- Brane
