RE: [Issue 4021] New - Need better error when slave is out-of-date

[Bert Huijben <be...@qqmail.nl>]

> -----Original Message-----
> From: philip@tigris.org [mailto:philip@tigris.org]
> Sent: zaterdag 17 september 2011 1:28
> To: issues@subversion.tigris.org
> Subject: [Issue 4021] New - Need better error when slave is out-of-date
> 
> http://subversion.tigris.org/issues/show_bug.cgi?id=4021
>                  Issue #|4021
>                  Summary|Need better error when slave is out-of-date
>                Component|subversion
>                  Version|---
>                 Platform|All
>                      URL|
>               OS/Version|All
>                   Status|NEW
>        Status whiteboard|
>                 Keywords|
>               Resolution|
>               Issue type|DEFECT
>                 Priority|P3
>             Subcomponent|libsvn_ra_serf
>              Assigned to|issues@subversion
>              Reported by|philip
> 
> 
> 
> 
> 
> 
> ------- Additional comments from philip@tigris.org Fri Sep 16 16:28:00
-0700
> 2011 -------
> When using a DAV write-through proxy the slave will be out-of-date w.r.t.
> the
> master immediately after a commit for a short period. During that period
> update
> in the committed working copy will fail because the committed parts are at
a
> newer revision than the slave.
> 
> Neon gives a more user-friendly error message than serf:
> 
> $ svn up wc2 --config-option servers:global:http-library=serf
> Updating 'wc2':
> svn: E175002: REPORT request on '/slave/!svn/vcc/default' failed: 500
> Internal
> Server Error
> 
> $ svn up wc2 --config-option servers:global:http-library=neon
> Updating 'wc2':
> svn: E000000: A reported revision is higher than the current repository
HEAD
> revision.  Perhaps the repository is out of date with respect to the
master
> repository?

Magic error code "0", that might be the/a cause of this problem.

	Bert