> I've upgraded TortoiseSVN from 1.5.8 to 1.6.1 and ran into following problem:
> 1. When I try to commit anything there from Explorer, everything works fine.
> 2. But when I try toing the same from different file manager (Far it is), even just launching TortoiseProc.exe /command:commit - I get 'Commit failed: '.' is not a working copy' error.
> 3. In file monitor I see that at some point TortoiseProc.exe is trying to access 'D:\WINDOWS\TEMP\.svn\entries', which surely doesn't exist.
> 4. In 1.5.8 I didn't have such a problem, but now I can't even fallback without re-checking out all working copies, since format have changed.
> Maybe it could be viewed not as a bug in TortoiseSVN, but I'd like to know what could've forced it to behave this way.
* Create the registry key HKCU\Software\TortoiseSVN\Debug as DWORD, set
its value to 1.
* get process explorer
Now, start the commit.
A dialog will first pop up, showing you the exact command line
TortoiseProc was started with. Ctrl-C in that dialog copies the whole
text to the clipboard - we need that text...
Then click OK on that dialog, wait for the commit dialog to show.
Open Process explorer, find the TortoiseProc.exe process, doublclick on
that process, go to the "image" tab of the process properties. We need
to know the content of "Path:", "Command line:" and most important,
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-04-23 13:26:40 CEST