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

Re: Issue with 1.4.0

From: Simon Large <simon_at_skirridsystems.co.uk>
Date: 2006-10-02 23:25:46 CEST

Thomas Hruska wrote:
> Ken Denault wrote:
>> I installed TortoiseSVN 1.4.0, Build 7501 - 32 Bit , 2006/09/15 21:34:55
>> last week and noticed that when files are modified the green check box
>> icon on the file never seems to change to the red exclamation point.
>> When I click on Commit from the popup menu all the modified files show
>> up in the list, so it appears the TSVN knows they have been updated.
>>
>> I don't remember this ever happening in prior versions.
>
> Oh good. I'm not the only one seeing this happen. Whenever I report a
> bug anymore, the devs get annoyed for whatever reason.

No need to be like that ;-)

> I'm seeing this mostly with directories and I've been able to repeat the
> bug by having a modified file in a subdirectory and then adding a new
> file in the main directory to SVN. When I do that, every icon changes
> to a green checkmark...including the '.svn' subdirectory in the main
> directory. Attached is a screenshot of what I mean. (I blacked out
> critical segments and drew on the image to indicate what the problems are).

That just jogged my memory. I upgraded from 1.3.5 to 1.4.0 and ran a
cleanup on all my WCs. All ok for a while, then I followed the sequence
you describe. Modified a file (more than 1? can't remember) and added a
file (more than 1? ...) At that point everything went green. Killing
TSVNCache fixed it, nothing else would.

It was not the same day that I upgraded, but I may well have left my PC
on, so TSVNCache would have been running on a 1.3.5 WC and not restarted
after the cleanup. Maybe that is how it got confused? I have not seen
the problem since.

> This bug seems to show up more often on removable media (e.g. USB
> thumbdrives) and it fixed itself one time on my main hard drive but only
> after I checked in my changes and it took about 2 minutes to get around
> to fixing itself. I haven't checked in the changes shown in the
> attached image since I upgraded to 1.4.0, but I have rebooted a couple
> times (due to Windows updates). So, this means the working copy is
> using the old 1.3.x format. It may correct itself when I check in my
> work, but that's a week away.

In my case it was on the hard drive. Try doing a WC cleanup, reboot and
see if it ever happens again.

Simon

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Oct 2 23:25:17 2006

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.