Re: Can no longer move files after relocate

[Hendrik Maryns <qw...@sneakemail.com>]

Hendrik Maryns schreef:
> Hendrik Maryns schreef:
>> Hi,
>>
>> I recently moved my svn:// repository from localhost to a machine in the
>> same network, called coxorange.  In the SVN repository exploring
>> perspective, I relocated the repo svn://localhost to svn://coxorange.
>>
>> Things went fine, I was able to commit and update, make a tag.
>>
>> Today, I decided to split a Java package in two packages.  I made the
>> new package, which was initially marked with a ‘?’.  I then tried to
>> move the classes over to the package, but Eclipse gives the error message
>>
>> An exception has been caught while processing the refactorying ‘Move’.
>>
>> Reason: Problems encountered while moving resources.
>>
>> At the same time, the svn console shows the following:
>>
>> move
>> /home/hendrik/workspace/MSO/de/uni_tuebingen/sfb/lichtenstein/binarytrees/Query.java 
>>
>> /home/hendrik/workspace/MSO/de/uni_tuebingen/sfb/lichtenstein/UI/Query.java 
>>
>>     svn: Cannot copy to
>> '/home/hendrik/workspace/MSO/de/uni_tuebingen/sfb/lichtenstein/UI', as
>> it is not from repository 'svn://coxorange/'; it is from 
>> 'svn://coxorange'
>>
>> I tried adding the / at the end of the repo name, but this didn’t help,
>> instead it split up the repo in three different ones for each project,
>> but the error message stays the same.
>>
>> I’d be pleased if someone helped me out of this.
> 
> Still nobody?
> 
> I had another problem to which I accidentally found the ‘solution’: I 
> was unable to commit changes to the directory 
> /home/hendrik/workspace/MSO/de/uni_tuebingen/sfb/lichtenstein/binarytrees/. 
>  Turns out it had an uncommitted property change for svn:ignore.  By 
> deleting this property change, I was able to commit normally.
> This probably is a bug, but I do not really know how to phrase it, maybe 
> one of the committers here can pick it up?
> 
> However, the moving of the file is still not possible, still with the 
> same error.

This seems to be a Subversion bug, since I get the same error on the 
command line.  Cross-posting and follow-up to subversion-user, hope to 
get an answer there.

H.
-- 
Hendrik Maryns
http://tcl.sfs.uni-tuebingen.de/~hendrik/
==================
http://aouw.org
Ask smart questions, get good answers:
http://www.catb.org/~esr/faqs/smart-questions.html