RE: Checksum mismatch still with 1.8.19

Thanks all for the responses.

Daniel wrote:
> Does it load successfully if you disable rep-sharing in fsfs.conf on the
> 1.8.19 repository?
>
I do not have rep-sharing enabled (on either repository).

>
> The two -1's imply that both sides of the collision are part of the same
> revision --- the revision that 'load' fails to commit. Inspect that revision on
> the 1.8.5 server. Does it, by any chance, really add two different files with
> the same sha1?
>
I inspected the revision. It does indeed have a number of files with the same MD-5 / SHA1 hash. The contents seem to be identical for them (they are NuGet packages.config files for different projects in the solution, all with the same package references, so their xml files are identical). But this is surely not an unusual situation?

Stefan wrote:
> Just quickly skimming through this mail, this sounds like the problem
> described and investigated in late July:
> http://mail-archives.apache.org/mod_mbox/subversion-users/201707.mbox/%3C5aae07a9-bb6d-6340-206a-dafcf91e35e6%40apache.org%3E
> Note that the issue reported in that mail was not fixed in 1.8.19 (it's
> currently expected to get into 1.8.20).
> If you are in fact running into that described problem, try svnadmin
> load -M 0 as a workaround. If that won't work, you are likely running
> into a different issue here. As danielsh already suggested, try to
> verify that indeed you don't have two different files with the same
> sha-1 hash (I doubt that atm, though).

I I had indeed read that thread before I posted here, however the last message on that thread said the fix would be in 1.8.19. Which is why I posted - that the fix is still pending is news to me :-)

I have tried the svnadmin load -M 0 trick, and that does seem to work to allow the dump to be loaded. Exactly why I have no clue though of course, but thanks! Is there any downside to this?

________________________________

This e-mail, including accompanying communications and attachments, is strictly confidential and only for the intended recipient. Any retention, use or disclosure not expressly authorised by Markit is prohibited. This email is subject to all waivers and other terms at the following link: http://www.markit.com/en/about/legal/email-disclaimer.page

Please visit http://www.markit.com/en/about/contact/contact-us.page for contact information on our offices worldwide.
Received on 2017-08-30 11:04:25 CEST