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

Re: [Subclipse-users] 0.9.106: File lost after update

From: Denny Valliant <valliant_at_unm.edu>
Date: 2006-02-25 01:54:00 CET

Christian Sell wrote:

>I just experienced a very disturbing incident with the 0.9.106 release. I am on
>Linux, using the JavaSVN client against a freshly installed 1.3 subversion
>repository on a Linux server via WebDAV/HTTPS.
>After entering the synchronize view, the view showed 2 conflicts which I decided
>I would resolve after the update. So I simply did an update.
>Afterwards I found that a file, which I had newly committed just before the
>update, and since modified, was now flagged as non-versioned! This file was not
>related to the conlicts I mentioned earlier. When I tried to do an update
>again, svn gave me an error message stating that it could not add the resource
>because another one of the same name was already existant!
>I ended up having to manually delete the directory in which the file was
>located, and doing an update on the parent directory. This added the file back
>to my working copy in versioned state. I then copied in the modifications, and
>was all set again. Still, I am having very mixed feelings.
>BTW, a colleague of mine reported similar experiences several times, from which
>he was only able to escape by deleting the working copy and doing a fresh
>The only real novelty that I can determine with my experience is the fact that I
>was using the sychronize view (which I dont do often), and that I did an update
>with merge conflicts.
>I hope this helps to resolve the issue
>Christian Sell
Thank you for the information, Christian.
    We've seen this in vary rare instances, and without recipe, so have
had trouble pinning it down. The general symptoms have been that you
commit some changes, they disappear from your working copy, but if you
synchronize, the changes will come down from the repo. Your colleague
could try that (update or sync prior to making a new WC), although if a
new WC resolves the issue permanently, that may also be a clue(?).

We are really interested in solving this issue, it's been rare, and
without recipe, so, as I said, hard to pin down. If you, or your
colleague, has any more relevant information, please let us know. (That
was a lot of commas. :-)


-PS I just kinda hang out on-list because I like subversion/subclipse so
much -- *NOT AN EXPERT* -- we'll see what the heavy hitters think, or if
they have other questions. You can also try using the javaHL adapter,
although it would be nice if we could get a solid recipe for reproduction.

To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Sat Feb 25 01:51:20 2006

This is an archived mail posted to the Subclipse Users mailing list.

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