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

[TSVN] Cache doesn't update status after a revert / revert bug

From: Lübbe Onken <l.onken_at_rac.de>
Date: 2005-02-09 10:01:29 CET

Hi Folks,

I think this has (partly) been reported before, but TortoiseSVN (Build 2642,
latest nightly) doesn't update its file and folder status after a revert.

I have a directory containing some modified files. The modified icons were
propagated up to the WC root. I selected revert on the WC root and let TSVN
revert all files, which the progess dialog happily tells me it did. Alas all
the file / folder status remain modified as before. F5 doesn't change
anything and if I select revert on the WC root again, all the files are
offered again. At this point I assume that revert worked and that just the
cache status is wrong.

Hm, switching to the dos shell:
'svn st' shows me that the files are modified even after running tsvn
revert. What can I believe now? This sounds like revert on the WC root
didn't revert files in a subdirectory even if they are shown in the revert
and progress dialog. Reverting a single file in tsvn yields the same result,
so it's a general revert / status problem.
Svn diff and tsvn diff both show that the files are really different, so
tsvn revert failed in both cases.

Trying to revert with the cl client now:
'svn revert *.h' does revert, because a 'svn st' doesn't list the .h files
anymore. So that seems to work. Tortoisesvn doesn't catch that status update
forced by the cl client, because the .h files are still shown as modified.
Tsvn diff and and svn diff don't show any differences in the files, so the
revert has worked

Now it's getting worse. I select 'tsvn revert' on my wc root again and the
files are shown again. Wh...

<sidenote>
Minutes later, while I am writing this, the cache crawler seems to have
reached my reverted files, because now the status switched to 'normal' up to
the WC root. Another reason for priority scheduling.
</sidenote>

...en I now 'tsvn revert' the files, they are back in the *modified* state.
Yes, no typo, *modified*. This sounds like tsvn revert is doing the opposite
of what it is supposed to do.
'Svn st', svn diff and tsvn diff confirm that the files are back to the
modified state.

This happened independently of the status that tsvn shows for the files, but
remember that I selected 'tsvn revert' before the status update happened.
9:45am: 'svn revert *.h*
I will now wait a few minutes until tsvn shows the normal overlays again and
select 'tsvn revert' when the status is normal.
9:50am: getting impatient. Filemon shows me that each time I hit F5,
TSVNCache scans all the entries in the directory, but the icon overlays
aren't updated. This sounds a bit like TSVNCaches inital status crawl has
caused the status change the first time it happened. Or was it a cache crash
that caused the cache to be restarted. Anyway. I'll use a bigger hammer and
kill the cache manually.
9:55am: TSVN Cache killed. Icons are getting refreshed. The modified status
is still there. 'svn st', 'svn diff' and 'tsvn diff' show no modifications

'tsvn revert' offers these files again.

9:58am: /me out of ideas
Anyone can explain the difference between svn and tsvn? I can e-mail you a
part of the WC, if it helps.

Cheers
- Lübbe

--
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Feb 9 10:02:19 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

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