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

Re: Bug: Lost reference to subversioned file when saving changes (only version 1.3.x)

From: Peter McNab <mcnab_p_at_melbpc.org.au>
Date: 2006-03-09 14:01:06 CET

Jirka Walter wrote:
> Hi developers,
>
> I have found a strange bug, that is caused by conjuction with the newest
> version of TortoiseSVN (1.3.1, 1.3.2) and concrete version of
> specialized file editor, Visual FoxPro 9.0
>
> TortoiseSVN losts reference to subversioned files (working copies), when
> saving changes to FoxPro form (for subversion: there are two files,
> *.SCX and *.SCT, maintained as application/octet-stream, because they
> are not txt, nor xml files, but single table file in DBase FoxPro
> format, DBF).
>
> = icon overlays disappear after save and no longer reappear, TortoiseSVN
> context menu offers only "Add file" and "Ignore file" options. I can
> wait for days, switch off the computer and switch it on again, but
> nothing changes.
>
> Okay, I do "SVN Commit" in parent folder and what I see? Files are
> versioned (I see them even if uncheck "Show unversioned files"), but
> marked as missing (in fact: text status = missing, property status =
> normal). So, I press the "Cancel" button and see, icon overlays on my
> files signalize "deleted" status (this will change only after commit).
>
> I have tried SVN Update, nothing changes.
>
> After successful SVN Commit, everything goes to correct state: icon
> overlays (not changed) and context menu.
>
> Funny, if I use different Visual FoxPro version (7.0) this does not
> happen (everything is OK).
>
> Possible reason - how VFP saves changes:
> 1) original file is deleted
> 2) new file is renamed from temporary name to original file name
> (example: j1to0014.tmp -> crm_akce2.scx)
> 3) for a short time interval the new file is exclusively locked (it
> can't be accessed even in read-only mode) - this did not happen in VFP
> 7.0 or time interval was shorter and renamed event occured after
> releasing the lock.
>
> We have tried TortoiseSVN version 1.2.6 - it works correctly.
>
> Can anybody help?
>
> P.S. sorry for my english (if it's bad)
>
>
Your English is pretty good.
Without analysing everything you mentioned, is there any chance that the
original file extents shown

*.SCX and *.SCT are getting changed by the editor to lowercase during the rename?

SVN is filename case sensitive, so a changed name is going to look like a file is missing.

Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Mar 9 14:07:02 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.