2009/4/15 Stefan Fuhrmann <stefanfuhrmann_at_alice-dsl.de>:
> Tobias Wildberg wrote:
>
>> >> I am using TortoiseSVN 1.6.1, Build 16129 - 32 Bit and whenever I
> call
>> >> "show log", the log viewer stops with the error message "File not
> found
>> >> revision xxx, path '/unk'". The original path it should be referenced
> to
>> >> has the name '/trunk'!
>> >>
>> >> This only occurs with working copies, which have been originally
> checked out
>> >> with TortoiseSVN versions 1.5 (or even older?). All working copies
> produced
>> >> by version 1.6.x don't have this problem, also browsing and calling
> the log
>> >> with the RepoBrowser in the server-side project works properly.
>>
>>
>> > Try clearing the log cache.
>>
>> When I disable the checkbox "Enable log caching" in the menu "Settings
> ->
>> Log caching -> Global settings" the log window appears correct. But if I
>> afterwards activate the log caching again, the problem is also back
> again,
>> even if I call "Update" before. A clearing of the "Log messages (Input
> dialog)"
>> and "Log messages (Show log dialog)" in the dialog "Saved Data" and
> deleting
>> the "Cached Repositories" does not change the occurence of this problem.
>
> Ok. It seems that the root cause is that the representation for
> file: URLs has recently changed (from file:///\\ to file:/// or so).
> As this is part of the working copy information, clearing the
> log cache will not change the situation.
>
> I will try to reproduce and fix the problem with on the next weekend.
> In the mean while, there are two ways to work around this:
>
> * disable the log cache
> * create a fresh working copy
>
>> Now my questions about these reactions:
>> 1. Is deactivating the log caching a workaround or the solution?
>
> It is literally a workaround: it bypasses the log cache in both
> directions (directly query the repository, don't store the result).
>
>> 2. Is log caching generally useful or should I always deactivate it?
>
> It is generally useful. In fact, the revision graph will not be
> usable for larger repositories without it.
>
>> 3. Have I done something wrong or is this a real bug?
>
> It is a real bug. Possibly in the SVN working copy upgrade code.
> But TSVN can work around it once I got it reproduced.
>
>> 4. Why does the deleting of the saved data and the cached repositories
> not help?
>
> Somewhere in the URL->(repository URL, relative path) translation
> the old, long notation gets used and causes 'trunk/' to be shortened
> to 'unk/' and subsequent SVN requests will fail. So, the bug seems
> to be in the URL interpretation code (not the actual caching part)
> and that URL is part of your WC.
>
> Could you run "svn info" on your WC and see what format is being
> used for 'URL' and 'Repository Root'?
Will TSVN->relocate help here if used to correct the file://
representation in the WC? It is certainly better than hand-editing the
.entries file.
Simon
--
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=1727958
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-04-15 16:31:59 CEST