On Thu, Jul 17, 2008 at 3:25 PM, steveking <steveking_at_gmx.ch> wrote:
> Mark Phippard wrote:
>>>
>>> The second problem:
>>>
>>> When I do an update on the project folder I get the following error:
>>>
>>> An internal error occurred during: "SVN Update".
>>> Attempted to beginRule: P/(removed), does not match outer scope rule:
>>> P/(removed)
>>>
>>> If the actual part after the P/ is useful I'd rather send it to an
>>> individual person than the whole mailing list. If I do an update on
>>> the src folder inside the project it works fine.
>>
>> You are not the only person to report this. We have not been able to
>> recreate it to fix it. If you have any ideas on the secret recipe to
>> reproduce let us know. When we see this kind of error, there is one
>> semi-obvious fix we can make. When we looked at code, that fix was
>> already in it. So we are at a loss as to what to do at the moment.
>
> I don't know much about Java and what can cause an internal error. But my
> guess is that it's the same issue we have with TSVN: a lot of crash reports
> sent in indicate memory corruption when updating/merging.
> I've sent a patch to the Subversion list to fix this:
> http://subversion.tigris.org/servlets/BrowseList?list=dev&by=thread&from=666740
>
> The patch has already been applied to trunk and has also been backported to
> 1.5.x.
>
> Of course, I'm not sure if that's really the problem, but from "internal
> error" and "update", that's what I immediately thought of because of the
> crash dumps I got from users.
Thanks, but this one is definitely just a bug in Subclipse (when used
in Eclipse 3.4).
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-07-17 21:35:18 CEST