Evan Driscoll wrote on Fri, Jan 27, 2012 at 10:31:32 -0600:
> On 1/27/2012 3:41, Daniel Shahaf wrote:
> > Evan Driscoll wrote on Thu, Jan 26, 2012 at 15:04:43 -0600:
> >> 1. Did removing rep-cache.db fix it, or is there still a potential for
> >>some latent repository corruption?
> >
> > Yes.
On 1/27/2012 3:41, Daniel Shahaf wrote:
> Evan Driscoll wrote on Thu, Jan 26, 2012 at 15:04:43 -0600:
>> 1. Did removing rep-cache.db fix it, or is there still a potential for
>>some latent repository corruption?
>
> Yes. rep-cache.db is used by the commit process. If that file was
> silentl
Hi,
I am running Subversion 1.7.2 64 bit installer from CollabNet on
Windows 7. The problem I'm experiencing can be seen in the output
below. In summary, svn status is returning incorrect results,
sometimes not showing that something has been modified and sometimes
not recognizing that I'm in a
Evan Driscoll wrote on Thu, Jan 26, 2012 at 15:04:43 -0600:
> 1. Did removing rep-cache.db fix it, or is there still a potential for
>some latent repository corruption?
Yes. rep-cache.db is used by the commit process. If that file was
silently corrupted, it's possible that the text: and prop
Jesse Pepper writes:
> In file
>
> 'D:\Development\SVN\Releases\TortoiseSVN-1.7.1\ext\subversion\subversion\libsvn_wc\update_editor.c'
> line 1582: assertion failed (action == svn_wc_conflict_action_edit ||
> action
> == svn_wc_conflict_action_delete || action ==
> svn_wc_conflict_action_repl