Hi
Thanks for your reply.
Hmmm, not sure if it's possible to recreate this mess-up using the
standard svn commands, since I was bouncing around between Explorer,
TortoiseSVN and Subclipse.
But the basic failure is that I ended up with a "modify-entry delete"
command that referenced a directory that did not exist either in the WC
or in the repository.
Regards, Noel.
Daniel Shahaf wrote:
> Noel Grandin wrote on Mon, 18 Aug 2008 at 16:28 +0200:
>
>> Hi
>>
>> I managed to mess up one of my projects such that subversion won't do
>> anything useful with my WC.
>> For example, cleanup gives me:
>>
>> /cleanup C:/Work/Data_Files/Eclipse3.1/BuildAndDocTools
>> svn: Error processing command 'modify-entry' in
>> 'C:\Work\Data_Files\Eclipse3.1\BuildAndDocTools'
>> svn: Error modifying entry for 'buildFiles'
>> svn: 'buildFiles' is not under version control/
>>
>>
>
> We recently fixed one instance of this error in r32467 and r32470. (They
> will probably be in 1.5.2.)
>
> Can you describe how to reproduce the errors you're seeing? (Preferably
> starting from an empty repository.)
>
> Thanks,
>
> Daniel
>
>
>> Note: these are messages from subclipse, but I got the same kind of
>> problem with TortoiseSVN, and in both cases, they're both calling down
>> to the svn-client API.
>>
>> In this case the "modify-entry" was a delete.
>>
>> I eventually managed to fix it by modifying .svn/log by hand, but it
>> would be nice if svn-cleanup also checked for "modify-entry" data that
>> references files or directories that do not exist, and then removed
>> those entries.
>>
>> Thanks, Noel.
>>
>> Disclaimer: http://www.peralex.com/disclaimer.html
>>
>>
>>
>>
>
>
Disclaimer: http://www.peralex.com/disclaimer.html
Received on 2008-08-19 15:58:12 CEST