On Thu, 13 Nov 2008, Berend Dekens wrote:
I just found out that the other machine holding the SVN repository was
recently updated. So after trying on that one I got the same error! (Which
ofcourse made me think)
It seems that SVN invokes a remote copy of the binary for reading the repo
and simply pipes back the results... So while I got an error telling me
libexpat was not found, the error originated from the other server...
That is both funny and concerning. I think you should bring this up on the
subversion mailinglist (or open a bug for it on the subversion bug
tracking system). More people may fall in this trap.
--
-- dag wieers, dag@xxxxxxxxxx, http://dag.wieers.com/ --
[Any errors in spelling, tact or fact are transmission errors]
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos