On Mon, Apr 10, 2017 at 10:21 AM, Alfred von Campe wrote:
> We are not quite ready to move to CentOS 7 yet, but hopefully will soon.
> However, I don’t understand why the dependencies are different for i686
> and x86_64 on the same CentOS 6 platform for Subversion 1.9.X. Up to
> version 1.9.4-1,
Hi Doug:
The reason is pretty simple: we develop embedded software for a 32-bit platform
and compile for both the target (using a cross compiler) and also natively so
we can run unit and integration tests on our CentOS workstations. Our
application is not (yet) 64-bit compatible. Now I know I
FWIW, I recently made the same decision for the packages we provide at
CollabNet. We have stopped providing 32-bit versions for all platforms.
Mark
On Tue, Apr 11, 2017 at 7:26 AM, Doug Robinson
wrote:
> Alfred:
>
> You can blame me for the decision to prune out the 32-bit platform support
> f
Alfred:
You can blame me for the decision to prune out the 32-bit platform support
from WANdisco.
I can easily admit to being premature, but I'm finding less demand for
32-bit and really
question why anyone would continue to run 32-bit at this time? If you
could help me understand
then perhaps I
Bert / Brane:
Thank you. Accurate as always!
The original poster just shared that setting the following in the Apache
config file did the trick:
SVNUseUTF8 On
So all set. Excellent.
Thank you.
Doug
On Tue, Apr 11, 2017 at 5:04 AM, Bert Huijben wrote:
> This message on the forum is 100%
This message on the forum is 100% about the server side configuration. The
client has no known problems encoding paths in a url, but the url specification
itself doesn’t document an explicit encoding and as such Apache Httpd has to do
the translation of the first part of the URL to the local pat
