Re: Repo for latest 1.9 svn binaries for 32-bit RHEL 6?

[Nico Kadel-Garcia]

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, WANdisco provided binaries for both architectures.
>
> Alfred

I'm not saying they are. I'm saying "maintaining the dependency chain
is a pain in the keister, requiring more updated versions of system
provided components that require dependencies to build the
dependencies". It adds up to a lot of work.

Re: Repo for latest 1.9 svn binaries for 32-bit RHEL 6?

[Alfred von Campe]

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 can run a 32-bit 
compiler on a 64-bit host OS, but we also need to support a bunch of older 
projects on our 32-bit infrastructure and we haven’t taken the time to qualify 
them all on x86_64.  I’m in the process of automating the CentOS 7 x86_64 
installation but have hit a few snags along the way.  Eventually (3-6 months) 
we will be moving to 64-bit CentOS 7 (or possibly 64-bit Ubuntu), but until 
then we will continue to use 32-bit CentOS 6.  So if it’s not too much of a 
hassle, I would really appreciate if you can turn the 32-bit CentOS 6 builds 
back on.

Thanks,
Alfred


> On Apr 11, 2017, at 8:26, Doug Robinson  wrote:
> 
> 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 can reverse that decision...
> 
> Thank you.
> 
> Doug
> 
> 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, WANdisco provided binaries for both architectures.
> 
> Alfred
> 
> 
> > On Apr 7, 2017, at 20:46, Nico Kadel-Garcia  > > wrote:
> >
> > On Fri, Apr 7, 2017 at 9:57 AM, Alfred von Campe  > > wrote:
> >> Does anyone on this list have a pointer to a repo that hosts the latest 
> >> 32-bit (i686) Subversion binaries for RHEL 6?  I’ve been using the 
> >> WANdisco SVN Repo 1.9 
> >> (http://opensource.wandisco.com/centos/6/svn-1.9/RPMS 
> >> ), but it only has 
> >> version 1.9.5-1 for 64-bit (x86_64).  The latest 32-bit binaries in that 
> >> repo are for version 1.9.4-1, which are almost a year old.
> >>
> >> Thanks,
> >> Alfred
> >
> > I tried, some time back, to publish SRPM building tools for
> > subersion-1.9.x and 1.8.x over at https://github.com/nkadel/ 
> > . I
> > eventually had to throw in the towel as the component dependencies for
> > compiling the latest Subversion exceeded my time to backport and
> > provide separate, system compatible builds of various libraries. But
> > you're welcome to poke them and take a shot at getting it to RHEL 6.
> >
> > I also admit that with RHEL 5 and CentOS 5 obsolete, CentOS 6 has also
> > gotten quite long in the tooth. Can you update to CentOS 7?
> 
> 
> 
> 
> -- 
> DOUGLAS B ROBINSON SENIOR PRODUCT MANAGER
> 
> T +1 925 396 1125 <>
> E doug.robin...@wandisco.com 
> 
> World Leader in Active Data Replication™
> Find out more wandisco.com 
> THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY AND MAY BE 
> PRIVILEGED
> 
> If this message was misdirected, WANdisco, Inc. and its subsidiaries, 
> ("WANdisco") does not waive any confidentiality or privilege. If you are not 
> the intended recipient, please notify us immediately and destroy the message 
> without disclosing its contents to anyone. Any distribution, use or copying 
> of this email or the information it contains by other than an intended 
> recipient is unauthorized. The views and opinions expressed in this email 
> message are the author's own and may not reflect the views and opinions of 
> WANdisco, unless the author is authorized by WANdisco to express such views 
> or opinions on its behalf. All email sent to or from this address is subject 
> to electronic storage and review by WANdisco. Although WANdisco operates 
> anti-virus programs, it does not accept responsibility for any damage 
> whatsoever caused by viruses being passed.
> 

Re: Repo for latest 1.9 svn binaries for 32-bit RHEL 6?

[Mark Phippard]

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
> 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 can reverse that decision...
>
> Thank you.
>
> Doug
>
> 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, WANdisco provided binaries for both architectures.
>>
>> Alfred
>>
>>
>> > On Apr 7, 2017, at 20:46, Nico Kadel-Garcia  wrote:
>> >
>> > On Fri, Apr 7, 2017 at 9:57 AM, Alfred von Campe 
>> wrote:
>> >> Does anyone on this list have a pointer to a repo that hosts the
>> latest 32-bit (i686) Subversion binaries for RHEL 6?  I’ve been using the
>> WANdisco SVN Repo 1.9 (http://opensource.wandisco.co
>> m/centos/6/svn-1.9/RPMS), but it only has version 1.9.5-1 for 64-bit
>> (x86_64).  The latest 32-bit binaries in that repo are for version 1.9.4-1,
>> which are almost a year old.
>> >>
>> >> Thanks,
>> >> Alfred
>> >
>> > I tried, some time back, to publish SRPM building tools for
>> > subersion-1.9.x and 1.8.x over at https://github.com/nkadel/. I
>> > eventually had to throw in the towel as the component dependencies for
>> > compiling the latest Subversion exceeded my time to backport and
>> > provide separate, system compatible builds of various libraries. But
>> > you're welcome to poke them and take a shot at getting it to RHEL 6.
>> >
>> > I also admit that with RHEL 5 and CentOS 5 obsolete, CentOS 6 has also
>> > gotten quite long in the tooth. Can you update to CentOS 7?
>>
>>
>
>
> --
> *DOUGLAS B ROBINSON* SENIOR PRODUCT MANAGER
>
> T +1 925 396 1125
> *E* doug.robin...@wandisco.com
>
> World Leader in Active Data Replication™
> *Find out more wandisco.com *
>
> THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY AND MAY BE
> PRIVILEGED
>
> If this message was misdirected, WANdisco, Inc. and its subsidiaries,
> ("WANdisco") does not waive any confidentiality or privilege. If you are
> not the intended recipient, please notify us immediately and destroy the
> message without disclosing its contents to anyone. Any distribution, use or
> copying of this email or the information it contains by other than an
> intended recipient is unauthorized. The views and opinions expressed in
> this email message are the author's own and may not reflect the views and
> opinions of WANdisco, unless the author is authorized by WANdisco to
> express such views or opinions on its behalf. All email sent to or from
> this address is subject to electronic storage and review by WANdisco.
> Although WANdisco operates anti-virus programs, it does not accept
> responsibility for any damage whatsoever caused by viruses being passed.
>



-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

Re: Repo for latest 1.9 svn binaries for 32-bit RHEL 6?

[Doug Robinson]

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 can reverse that decision...

Thank you.

Doug

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, WANdisco provided binaries for both architectures.
>
> Alfred
>
>
> > On Apr 7, 2017, at 20:46, Nico Kadel-Garcia  wrote:
> >
> > On Fri, Apr 7, 2017 at 9:57 AM, Alfred von Campe 
> wrote:
> >> Does anyone on this list have a pointer to a repo that hosts the latest
> 32-bit (i686) Subversion binaries for RHEL 6?  I’ve been using the WANdisco
> SVN Repo 1.9 (http://opensource.wandisco.com/centos/6/svn-1.9/RPMS), but
> it only has version 1.9.5-1 for 64-bit (x86_64).  The latest 32-bit
> binaries in that repo are for version 1.9.4-1, which are almost a year old.
> >>
> >> Thanks,
> >> Alfred
> >
> > I tried, some time back, to publish SRPM building tools for
> > subersion-1.9.x and 1.8.x over at https://github.com/nkadel/. I
> > eventually had to throw in the towel as the component dependencies for
> > compiling the latest Subversion exceeded my time to backport and
> > provide separate, system compatible builds of various libraries. But
> > you're welcome to poke them and take a shot at getting it to RHEL 6.
> >
> > I also admit that with RHEL 5 and CentOS 5 obsolete, CentOS 6 has also
> > gotten quite long in the tooth. Can you update to CentOS 7?
>
>


-- 
*DOUGLAS B ROBINSON* SENIOR PRODUCT MANAGER

T +1 925 396 1125
*E* doug.robin...@wandisco.com

-- 


World Leader in Active Data Replication™
*Find out more wandisco.com *

THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY AND MAY BE 
PRIVILEGED

If this message was misdirected, WANdisco, Inc. and its subsidiaries, 
("WANdisco") does not waive any confidentiality or privilege. If you are 
not the intended recipient, please notify us immediately and destroy the 
message without disclosing its contents to anyone. Any distribution, use or 
copying of this email or the information it contains by other than an 
intended recipient is unauthorized. The views and opinions expressed in 
this email message are the author's own and may not reflect the views and 
opinions of WANdisco, unless the author is authorized by WANdisco to 
express such views or opinions on its behalf. All email sent to or from 
this address is subject to electronic storage and review by WANdisco. 
Although WANdisco operates anti-virus programs, it does not accept 
responsibility for any damage whatsoever caused by viruses being passed.

Re: Using UTF8 in repository name?

[Doug Robinson]

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% 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 path. When this fails you see errors as in this forum post.
>
>
>
> The part after the repository location is 100% handled inside the
> Subversion code and is always UTF-8 safe as it has no relation to real
> on-disk paths.
>
>
>
> On platforms like MAC/OS or Windows the server handles UTF-8 paths
> directly, but on unix based platforms like Linux where paths are at the
> core just formed by a bunch of bytes without a special meaning, you have to
> use a proper configuration. If the configuration mismatches there is no way
> to convert from the path form to UTF-8 and the other way around.
>
>
>
> Bert
>
>
>
> *From:* Doug Robinson [mailto:doug.robin...@wandisco.com]
> *Sent:* maandag 10 april 2017 22:17
> *To:* Branko Čibej 
> *Cc:* users@subversion.apache.org
> *Subject:* Re: Using UTF8 in repository name?
>
>
>
> Brane:
>
>
>
> Thank you for replying.  Based on this post:
>
>
>
> https://www.svnforum.org/forum/opensource-subversion-
> forums/general-setup-and-troubleshooting/79832-why-
> repository-name-should-not-be-utf-8
>
>
>
> I am wondering if the SVN client is properly URL-encoding the repository
> name?
>
>
>
> Based on:
>
>
>
> https://en.wikipedia.org/wiki/Percent-encoding
>
>
>
> I'm beginning to wonder if it is even possible (sort of similar to what
> Mac/OS does to UTF8 text...)?
>
>
>
> Thank you.
>
>
>
> Doug
>
>
>
> On Mon, Apr 10, 2017 at 8:53 AM, Branko Čibej  wrote:
>
> On 10.04.2017 14:44, Doug Robinson wrote:
> > Folks:
> >
> > I understand that UTF8 is the standard inside of Subversion repositories.
> > My question is whether having the repository name itself be UTF8?  For
> > instance zh_CN.utf8 ?  I googled around a bit and don't see an answer.
> >
> > If it is supported, is there some Apache setting that is required?
> >
> > Thanks in advance.
>
> As long as the underlying filesystem supports it, there should be no
> problems.
>
> -- Brane
>
>
>
>
>
> --
>
> *DOUGLAS B ROBINSON* SENIOR PRODUCT MANAGER
>
>
>
> *T* +1 925 396 1125 <(925)%20396-1125>
>
> *E* doug.robin...@wandisco.com
>
>
>
> World Leader in Active Data Replication™
>
> Find out more *wandisco.com *
>
> THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY AND MAY BE
> PRIVILEGED
>
> If this message was misdirected, WANdisco, Inc. and its subsidiaries,
> ("WANdisco") does not waive any confidentiality or privilege. If you are
> not the intended recipient, please notify us immediately and destroy the
> message without disclosing its contents to anyone. Any distribution, use or
> copying of this email or the information it contains by other than an
> intended recipient is unauthorized. The views and opinions expressed in
> this email message are the author's own and may not reflect the views and
> opinions of WANdisco, unless the author is authorized by WANdisco to
> express such views or opinions on its behalf. All email sent to or from
> this address is subject to electronic storage and review by WANdisco.
> Although WANdisco operates anti-virus programs, it does not accept
> responsibility for any damage whatsoever caused by viruses being passed.
>



-- 
*DOUGLAS B ROBINSON* SENIOR PRODUCT MANAGER

T +1 925 396 1125
*E* doug.robin...@wandisco.com

-- 


World Leader in Active Data Replication™
*Find out more wandisco.com *

THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY AND MAY BE 
PRIVILEGED

If this message was misdirected, WANdisco, Inc. and its subsidiaries, 
("WANdisco") does not waive any confidentiality or privilege. If you are 
not the intended recipient, please notify us immediately and destroy the 
message without disclosing its contents to anyone. Any distribution, use or 
copying of this email or the information it contains by other than an 
intended recipient is unauthorized. The views and opinions expressed in 
this email message are the author's own and may not reflect the views and 
opinions of WANdisco, unless the author is authorized by WANdisco to 
express such views or opinions on its behalf. All email sent to or from 
this address is subject to electronic storage and review by WANdisco. 
Although WANdisco operates anti-virus programs, it does not accept 
responsibility for any damage whatsoever caused by viruses being passed.

RE: Using UTF8 in repository name?

[Bert Huijben]

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 path. When this fails 
you see errors as in this forum post.

 

The part after the repository location is 100% handled inside the Subversion 
code and is always UTF-8 safe as it has no relation to real on-disk paths.

 

On platforms like MAC/OS or Windows the server handles UTF-8 paths directly, 
but on unix based platforms like Linux where paths are at the core just formed 
by a bunch of bytes without a special meaning, you have to use a proper 
configuration. If the configuration mismatches there is no way to convert from 
the path form to UTF-8 and the other way around.

 

Bert

 

From: Doug Robinson [mailto:doug.robin...@wandisco.com] 
Sent: maandag 10 april 2017 22:17
To: Branko Čibej 
Cc: users@subversion.apache.org
Subject: Re: Using UTF8 in repository name?

 

Brane:

 

Thank you for replying.  Based on this post:

 

https://www.svnforum.org/forum/opensource-subversion-forums/general-setup-and-troubleshooting/79832-why-repository-name-should-not-be-utf-8

 

I am wondering if the SVN client is properly URL-encoding the repository name?

 

Based on:

 

https://en.wikipedia.org/wiki/Percent-encoding

 

I'm beginning to wonder if it is even possible (sort of similar to what Mac/OS 
does to UTF8 text...)?

 

Thank you.

 

Doug

 

On Mon, Apr 10, 2017 at 8:53 AM, Branko Čibej  > wrote:

On 10.04.2017 14:44, Doug Robinson wrote:
> Folks:
>
> I understand that UTF8 is the standard inside of Subversion repositories.
> My question is whether having the repository name itself be UTF8?  For
> instance zh_CN.utf8 ?  I googled around a bit and don't see an answer.
>
> If it is supported, is there some Apache setting that is required?
>
> Thanks in advance.

As long as the underlying filesystem supports it, there should be no
problems.

-- Brane





 

-- 

DOUGLAS B ROBINSON SENIOR PRODUCT MANAGER

 

T +1 925 396 1125

E   doug.robin...@wandisco.com

 

   

World Leader in Active Data Replication™

Find out more   wandisco.com

THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY AND MAY BE 
PRIVILEGED

If this message was misdirected, WANdisco, Inc. and its subsidiaries, 
("WANdisco") does not waive any confidentiality or privilege. If you are not 
the intended recipient, please notify us immediately and destroy the message 
without disclosing its contents to anyone. Any distribution, use or copying of 
this email or the information it contains by other than an intended recipient 
is unauthorized. The views and opinions expressed in this email message are the 
author's own and may not reflect the views and opinions of WANdisco, unless the 
author is authorized by WANdisco to express such views or opinions on its 
behalf. All email sent to or from this address is subject to electronic storage 
and review by WANdisco. Although WANdisco operates anti-virus programs, it does 
not accept responsibility for any damage whatsoever caused by viruses being 
passed.