WC state problems

[David Balazic-2]

Hi!

I use subclipse 1.6.5 with Eclipse Java EE v3.4.2 (M20090211-1700).

It happens "all the time", that SVN is confused, when something in the
working is not as it would like it. Example:
 - I delete a folder with contents.
 - I call Team / Cleanup on the parent project

I get:

org.tigris.subversion.javahl.ClientException: Path is not a working copy directory
svn: 'F:\data\eclipseWS\X\Y\Z' is not a working copy directory

org.tigris.subversion.javahl.ClientException: Path is not a working copy directory
svn: 'F:\data\eclipseWS\X\Y\Z' is not a working copy directory

(the same error twice)

The directory has been since recreated by the build process, but the .svn folders are missing.

So why is SVN not able to resolve this situation? It keeps repeating the above error
each time I run "Cleanup".


Other details:
JavaHL 1.6.5
Subversion Client Adapter 1.6.4.1

OS: Windows XP Pro SP3
Java :
 java version "1.6.0_15"
Java(TM) SE Runtime Environment (build 1.6.0_15-b03)
Java HotSpot(TM) Client VM (build 14.1-b02, mixed mode, sharing)


Regards,
David

---------------------------------------------------------------------
http://www.nosoftwarepatents.com         Innovation, not litigation !
---
David Balažic                 mailto:david.balazic@...
HERMES Softlab                http://www.hermes-softlab.com
Zagrebska cesta 104           Phone: [phone]
SI-2000 Maribor
Slovenija
---------------------------------------------------------------------
"Be excellent to each other." -
Bill S. Preston, Esq. & "Ted" Theodore Logan
---------------------------------------------------------------------

------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2404950

To unsubscribe from this discussion, e-mail: [users-unsubscribe@...].

[Mark Phippard-3]

On Thu, Oct 8, 2009 at 9:14 AM, David Balažic
<david.balazic@...> wrote:

> I use subclipse 1.6.5 with Eclipse Java EE v3.4.2 (M20090211-1700).
>
> It happens "all the time", that SVN is confused, when something in the
> working is not as it would like it. Example:
>  - I delete a folder with contents.
>  - I call Team / Cleanup on the parent project

Cleanup is a very-specific Subversion command that only cleans up
after certain Subversion commands that are killed in the middle of
running.

> org.tigris.subversion.javahl.ClientException: Path is not a working copy directory
> svn: 'F:\data\eclipseWS\X\Y\Z' is not a working copy directory
>
> org.tigris.subversion.javahl.ClientException: Path is not a working copy directory
> svn: 'F:\data\eclipseWS\X\Y\Z' is not a working copy directory
>
> (the same error twice)
>
> The directory has been since recreated by the build process, but the .svn folders are missing.
>
> So why is SVN not able to resolve this situation? It keeps repeating the above error
> each time I run "Cleanup".

If you delete .svn folders your working copy is broken and cannot be
repaired other than via checkout.  In some cases, you can remove the
folder that is missing the .svn folder and then run svn update on a
parent and it will recreate it.  I think that might actually only work
with missing files though.

Subversion 1.7 is rewriting the working copy code to remove the .svn
folders.  This will immediately make all problems like this disappear.

For now, it is your responsibility to make sure you do not do things
that delete or alter the .svn folders.

--
Thanks

Mark Phippard
http://markphip.blogspot.com/

------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2404952

To unsubscribe from this discussion, e-mail: [users-unsubscribe@...].

[Johan Compagner]

If you delete .svn folders your working copy is broken and cannot be
repaired other than via checkout.  In some cases, you can remove the
folder that is missing the .svn folder and then run svn update on a
parent and it will recreate it.  I think that might actually only work
with missing files though.

Subversion 1.7 is rewriting the working copy code to remove the .svn
folders.  This will immediately make all problems like this disappear.

For now, it is your responsibility to make sure you do not do things
that delete or alter the .svn folders.

ahhh!

that would fix way more problems i think like svn folder move from one to the other (where i just want to copy as new)

The patch that i created also does work fine but under mac there where some weird locking problems..

But if there are no more svn folders.. where is everything stored now?

Only the root gets the info?

[Mark Phippard-3]

On Thu, Oct 8, 2009 at 9:43 AM, jcompagner <jcompagner@...> wrote:

>
>> If you delete .svn folders your working copy is broken and cannot be
>> repaired other than via checkout.  In some cases, you can remove the
>> folder that is missing the .svn folder and then run svn update on a
>> parent and it will recreate it.  I think that might actually only work
>> with missing files though.
>>
>> Subversion 1.7 is rewriting the working copy code to remove the .svn
>> folders.  This will immediately make all problems like this disappear.
>>
>> For now, it is your responsibility to make sure you do not do things
>> that delete or alter the .svn folders.
>>
>
> ahhh!
>
> that would fix way more problems i think like svn folder move from one to
> the other (where i just want to copy as new)
>
> The patch that i created also does work fine but under mac there where some
> weird locking problems..
>
> But if there are no more svn folders.. where is everything stored now?
>
> Only the root gets the info?

For 1.7, there will be a single .svn folder in the root of the working
copy.  In a future version, there is a plan to allow the metadata to
live in your $HOME or anywhere.  IOW, you could have a single .svn
folder for all of your working copies.  This would also enable things
like sharing the pristine copies.  So if you had three copies of trunk
checked out, there would only be one extra copy of the pristine files.
 And eventually, checkout would even be smart enough to not ask the
server for the files it already has.

--
Thanks

Mark Phippard
http://markphip.blogspot.com/

------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2404965

To unsubscribe from this discussion, e-mail: [users-unsubscribe@...].