On 1/9/14, 2:06 PM, Антон Бреусов wrote: > 1. An issue: > - When checking out (or updating) a repository with a lot of small html and > PHP > files (it's a Drupal software tree with a lot of vendor branches used for > keeping site configuration up to date) a Checksum mismatch message appears for > one of files: > > A vendor\drupal\current\modules\php\php.info <http://php.info> > A vendor\drupal\current\modules\php\php.install > A vendor\drupal\current\modules\translation\translation.module > A vendor\drupal\current\modules\translation\translation.test > svn: E200014: Checksum mismatch for > 'D:\TEMP\_SVN\test1_1\vendor\drupal\current\modules\update\tests\aaa_update_test.tar.gz': > expected: 02ede29e316cddf45ee6535ff02eae1d > actual: c349cea43c4af6f1192c8eb62a5b27ab
The problem is a misconfigured http server, with a mis-configuration that wouldn't turn up until 1.8.5 when we adjusted the filename entry on the request record in httpd actually not be garbage or empty. This change is described in this release note: https://subversion.apache.org/docs/release-notes/1.8.html#mod_dav_svn-fsmap I downloaded your file. $ md5 aaa_update_test.tar.gz MD5 (aaa_update_test.tar.gz) = 02ede29e316cddf45ee6535ff02eae1d You'll note that's the expected checksum as mentioned in the error above. $ gzip -dc aaa_update_test.tar.gz | md5 c349cea43c4af6f1192c8eb62a5b27ab You'll note that's the checksum in the actual result received. What's happening is your httpd server is configured to add the gzip encoding to the headers of files being served that have filenames that end in .gz. Typically you'll see that setup on the server with something like this: AddEncoding x-gzip .gz AddEncoding x-compress .Z AddEncoding is part of mod_mime and is documented here: https://httpd.apache.org/docs/current/mod/mod_mime.html#addencoding Those sorts of configurations should never apply to the Location being used to serve Subversion.
