[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SHA-1 collision in repository?

From: Philip Martin <philip_at_codematters.co.uk>
Date: Sat, 24 Feb 2018 01:13:31 +0000

Myria <myriachan_at_gmail.com> writes:

> I was able to branch (svn copy) the affected branch to a new branch,
> and committing the same file to the new branch has the same error.
> Checking out that revision works fine; only that commit is affected.

I suspect the problem is that the repository revision files are OK but
that the rep-cache mapping is corrupt. You would need server-side
access to verify this.

There are a couple of options:

  A) disable rep-caching by editing fsfs.conf inside the repository

  B) reset the mapping by deleting/renaming the file db/rep-cache.db
     inside the repository (but please rename rather than delete if you
     want to help us identify the corruption)

Doing either of these should allow the commit to succeed.

-- 
Philip
Received on 2018-02-24 02:13:39 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.