I was already using .108 release which I installed yesterday morning. So it was .108 that produced the problem. Also, I was NOT using Sync View, but I was using the menu item "Team -> Edit Conflicts" directly from the package explorer. A new checkout surely will solve my local problems, but as I wrote before, my intention is to keep the screwed state as long as possible to allow you to find out the actual bug and fix it. That way, my crash would help to improve subclipse. So is there anything I shall check or try for you?
Von: Mark Phippard [mailto:email@example.com]
Gesendet: Di 28.02.2006 17:23
Betreff: Re: [Subclipse-users] AW: Subclipse drives me crazy
"Markus Karg" <firstname.lastname@example.org> wrote on 02/28/2006 10:10:18 AM:
> sorry for posting to the wrong list.
> I checked it and now I am scared a bit.
> The "unversioned files" are really marked as "unversioned" in Subclipse,
> actually those had been versioned before the merge and no one removed
> from the repository.
> So it looks somehow Subclipse made SVN to "forget" about files.
> That's really strange.
> What to do to prevent this in future?
If you work from the Synchronize view there was a bug in the update
process that could have potentially caused this, essentially it was
back-revisioning your WC. So if the revision went back to one where those
files did not exist, they could be removed. If they had local
modifications at the time, then they become unversioned. This was fixed
in 0.9.108 which was released yesterday.
To fix, the easiest thing to do would be a new checkout. Otherwise,
delete/move all of the unversioned files and then do Team -> Update to put
them back. If you had pending changes, you would then have to copy back
the files you previously moved.
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Mar 1 07:58:58 2006