[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: Mark Phippard <markp_at_softlanding.com>
Date: 2006-02-25 02:00:31 CET

> Afterwards I found that a file, which I had newly committed just before
> update, and since modified, was now flagged as non-versioned!

What did the Console view say that it had done? The behavior you describe
sounds exactly like what would happen if the file had been deleted in the
repository. Since you had made local modifications, the file does not get
deleted, it just becomes unversioned because there is no longer a
repository file.

> When I tried to do an update
> again, svn gave me an error message stating that it could not add the
> because another one of the same name was already existant!

If someone deleted the file and commited, then you did update, then someone
else added the file back and committed, and then you did your update again,
this is what would happen.

I am not saying this is what happened, but it is one scenario where
everything would sound correct. Running Show in Resource History on a
parent folder should reveal if this is what happened.

> 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
> with merge conflicts.

Neither of those factors would effect the behavior of the update command.
Just fyi...


Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Sat Feb 25 02:01:04 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.