Erik Huelsmann wrote:
> On 10/24/07, Chris 'Xenon' Hanson <xenon@3dnature.com> wrote:
>> To follow up on this situation, which I haven't yet resolved, it appears that sometimes
>> the "all-wcprops" file does not get updated during a check-in. This does not get resolved
>> by any amount of updating or "Clean Up" operations. Having someone else check in a change
>> to the modified file and then updating to get that change seems to sort things out sometimes.
>>
>> It occurs while using TortoiseSVN or AnkhSVN, so it seems to be non-client-specific.
>>
>> What I'm stuck on now is determining _why_ this happens, and what to do about it. I am
>> unclear about where to look for more debugging info, and whether I should be debugging the
>> client or the server.
>
> Ok. What I was able to grasp from the sources is that an update of
> all-wcprops is triggered by the response sent by the server when
> committing (MERGE http-request). If you would be able to capture the
> network trace of the commit which isn't correctly updating some files,
> we could try to figure out whether the wc-prop-update instruction is
> missing from the response (meaning we have to search for the cause in
> the server) or that maybe the response is truncated or that there are
> other reasons why the wcprop isn't updated.
I will fire up Ethereal and try to do capture a minor operation.
Thanks for the analysis and suggestion.
> HTH,
> Erik.
--
Chris 'Xenon' Hanson | Xenon @ 3D Nature | http://www.3DNature.com/
"I set the wheels in motion, turn up all the machines, activate the programs,
and run behind the scenes. I set the clouds in motion, turn up light and sound,
activate the window, and watch the world go 'round." -Prime Mover, Rush.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 24 23:44:28 2007