Write-through proxy issue with libneon.

[Nils Krabshuis <Ni...@redwood.com>]

Hi,
 
When trying to commit to a 'slaved' repository with 'proxy
write-through' feature everything goes well unless someone tries to add
a new file on a slave.
All other commits (changes etc) get through just fine.
 
After a couple of hours of short-circuiting this problem I discovered
that it was actually a "client" problem, as I was capable of adding new
files to the repository with the client on Os-X.
Comparing the binaries on Os-X and on Ubuntu Hardy Heron I discovered
that the os-x client uses libserf, and the Ubuntu one uses libneon.
 
To verify that this was indeed the problem, I downloaded the source, and
compiled it, one version against libneon, the other one against libserf.
The libserf version works, the libneon version has the before-mentioned
restriction.
 
This issue occurs with any version >= 1.5.0.
 
My testing systems:
- Ubuntu Hardy Heron 
- Ubuntu Intrepid Ibex
- Os-X 
 
On Ubuntu, the packages used on hardy are the ones from backports
(1.5.1), which are linked against ONLY libneon, since libserf is only
available in Universe.
Intrepid, it's just in 'main', but it's also linked against libneon, for
the same reason.
 
people reporting similar issues without a solution:
 
http://svn.haxx.se/users/archive-2008-08/0235.shtml (see the rest of the
thread as well)
http://www.nabble.com/Problem-with-write-through-mirroring-on-subversion
-1.5.1-p18762134.html
http://webui.sourcelabs.com/subversion/mail/user/threads/problems_with_s
vn1.5_write-through-proxy.meta
 
etc. etc.
 
So far, as mentioned, the only work-around I have found is to link
explicately against libserf and not libneon to make this feature behave
properly.
 
Kind regards,
Nils