Re: working copy locked after move

> He Alexander,
>
>    as I urgently needed that wc back working I checked out a fresh one
> and manually merged the changes.  But what I can do is, set up a smaller
> toy wc, try to reproduce the error and e-mail that wc.  What that be
> alright with you?
>
> Cheers,
>  /nm
>
> Alexander Sinyushkin wrote:
>> Hello Normen,
>>
>> Is it possible to upload that wc to some ftp:// server or, for
>> example, to depositfiles.com (allows maximum 300MB files)?
>> ----
>> Alexander Sinyushkin,
>> TMate Software,
>> http://svnkit.com/ - Java [Sub]Versioning Library!
>>
>> Normen Müller wrote:
>>> Great that you guys really want to help me, cause right now I am
>>> really desperate. I really need this wc, cause I did quite some
>>> changes.  I would like to send you this wc, it's to large, though!
>>> :-(  Quite a hundred of megabytes... So e-mail doesn't work.  Any
>>> thing else I could do?
>>>
>>> Alexander Kitaev wrote:
>>>> Hello Normen,
>>>>
>>>>  > I think the problem is, that before I also did all that, I
>>>> performed an
>>>>  > 'svn st' (not jsvn st).  So I accidentally used the old client.  
>>>> Then
>>>>  > switching back to jsvn I get the following error message:
>>>>  >
>>>>  > svn: Log entry missing name attribute (entry 'modify-wcprop' for
>>>>  > directory 'doc/blue/dep')
>>>> st(atus) is readonly operation and shouldn't affect working copy in
>>>> any way. Old client (both svn and jsvn) should just fail when
>>>> invoked on the new working copy.
>>>>
>>>> So, I'd follow Alex's advice - please send us your working copy (one
>>>> on with incorrect log entry and one for which "wc is locked" error
>>>> reported). Definitely there are still bugs in SVNKit trunk and
>>>> working copy will help to reproduce them.
>>>>
>>>> Alexander Kitaev,
>>>> TMate Software,
>>>> http://svnkit.com/ - Java [Sub]Versioning Library!
>>>>
>>>> Normen Müller wrote:
>>>>> Alexander Sinyushkin wrote:
>>>>>> Hello Normen,
>>>>>>
>>>>>> I've just tried a similar scenario:
>>>>>>
>>>>>> 1. created a dir in an existing wc with the command 'jsvn mkdir
>>>>>> examples'
>>>>>>
>>>>>> 2. then I moved two different directories into the examples
>>>>>> directory. Both are on the same level as the examples directory is:
>>>>>>
>>>>>> alex@UFO:~/workspace/tmp/wc$ alex@UFO:~/workspace/tmp/wc$
>>>>>> $JSVN_PATH mv bbc examples
>>>>>> A         examples/bbc
>>>>>> D         bbc/cnn
>>>>>> D         bbc
>>>>>> alex@UFO:~/workspace/tmp/wc$ $JSVN_PATH mv tt examples
>>>>>> A         examples/tt
>>>>>> D         tt
>>>>>>
>>>>>> 3. And afterwards I launched a commit command which succeeded:
>>>>>>
>>>>>> alex@UFO:~/workspace/tmp/wc$ $JSVN_PATH ci -m "test"
>>>>>> Deleting       bbc
>>>>>> Adding         examples
>>>>>> Adding         examples/bbc
>>>>>> Deleting       examples/bbc/cnn/new_republic
>>>>>> Adding         examples/tt
>>>>>> Deleting       tt
>>>>>>
>>>>>> Committed revision 29.
>>>>>>
>>>>>> So, can you provide more details on the problem? For example,
>>>>>> which version of SVNKit did you use, how exactly did you invoke mv
>>>>>> commands, what did the wc look like (tree). Maybe it will be more
>>>>>> useful to send us that working copy on which commit fails (unless
>>>>>> it is huge or you can not send it to us).
>>>>>> ----
>>>>>> Alexander Sinyushkin,
>>>>>> TMate Software,
>>>>>> http://svnkit.com/ - Java [Sub]Versioning Library!
>>>>>>
>>>>>> Normen Müller wrote:
>>>>>>> Dear SVNKit,
>>>>>>>
>>>>>>>    I haven't figures out what exactly the problem is, but let's
>>>>>>> assume the following scenario:
>>>>>>>
>>>>>>> ~/vc/wc
>>>>>>> ~/vc/wc/exa
>>>>>>> ~/vc/wc/exa
>>>>>>>
>>>>>>> So I checked out a working copy wc to my local directory ~/vc.  
>>>>>>> In the next step, I 'jsvn mkdir' a new directory 'examples',
>>>>>>> resulting in ~/vc/wc/examples.  Then I 'jsvn mv' exa and exb to
>>>>>>> examples.  But when I want to commit all changes on ~/vc/wc, jsvn
>>>>>>> tells me the working copy would be locked, but 'jsvn st' output
>>>>>>> doesn't.  The 'jsvn st' output looks correct: delete for exa and
>>>>>>> exb, and an add for examples/exa and examples/exb.
>>>>>>>
>>>>>>>    Committing each modification by it own works, though.
>>>>>>>
>>>>>>> Any clue?
>>>>>>>
>>>>>>> Cheers,
>>>>>>>  /nm
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> To unsubscribe, e-mail: svnkit-users-unsubscribe@...
>>>>>>> For additional commands, e-mail: svnkit-users-help@...
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: svnkit-users-unsubscribe@...
>>>>>> For additional commands, e-mail: svnkit-users-help@...
>>>>>>
>>>>> I think the problem is, that before I also did all that, I
>>>>> performed an 'svn st' (not jsvn st).  So I accidentally used the
>>>>> old client.  Then switching back to jsvn I get the following error
>>>>> message:
>>>>>
>>>>> svn: Log entry missing name attribute (entry 'modify-wcprop' for
>>>>> directory 'doc/blue/dep')
>>>>>
>>>>> and the entire wc is locked.  I have no change to revert these
>>>>> changes :-(
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: svnkit-users-unsubscribe@...
>>>>> For additional commands, e-mail: svnkit-users-help@...
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: svnkit-users-unsubscribe@...
>>>> For additional commands, e-mail: svnkit-users-help@...
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: svnkit-users-unsubscribe@...
>>> For additional commands, e-mail: svnkit-users-help@...
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: svnkit-users-unsubscribe@...
>> For additional commands, e-mail: svnkit-users-help@...
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: svnkit-users-unsubscribe@...
> For additional commands, e-mail: svnkit-users-help@...
>
>
>