Re: EOL problems in cvs2svn converted repository

2018-02-12 Thread Bo Berglund
On Sun, 11 Feb 2018 17:49:32 +0100, Bo Berglund wrote: >Any advice? Thanks for all advice and links. Most helpful. I have now mastered the way the svn_apply_autoprops.py can be used and have completed the EOL configuration of the repository for contractors with all items

Re: EOL problems in cvs2svn converted repository

2018-02-11 Thread Ryan Schmidt
On Feb 11, 2018, at 10:49, Bo Berglund wrote: > On Sun, 11 Feb 2018 08:45:17 +, Daniel Shahaf wrote: > >> Bo Berglund wrote on Sun, 11 Feb 2018 09:34 +0100: >>> For OpenVPN I found that I had to add some servers to apt-get in order >>> to use the OpenVPN own repository, is there a similar

Re: EOL problems in cvs2svn converted repository

2018-02-11 Thread Bo Berglund
On Sun, 11 Feb 2018 08:45:17 +, Daniel Shahaf wrote: >Bo Berglund wrote on Sun, 11 Feb 2018 09:34 +0100: >> For OpenVPN I found that I had to add some servers to apt-get in order >> to use the OpenVPN own repository, is there a similar solution for >> Subversion? >

Re: EOL problems in cvs2svn converted repository

2018-02-11 Thread Daniel Shahaf
Bo Berglund wrote on Sun, 11 Feb 2018 09:34 +0100: > For OpenVPN I found that I had to add some servers to apt-get in order > to use the OpenVPN own repository, is there a similar solution for > Subversion? See https://subversion.apache.org/packages ... but unless there is a specific bugfix from

Re: EOL problems in cvs2svn converted repository

2018-02-11 Thread Bo Berglund
On Sun, 11 Feb 2018 08:40:06 +0100, Bo Berglund wrote: >OK, >then I will have to test on a Linux machine. The problem here is that >I need to connect VPN to the server from Linux. So I have more >research to do for that >The Linux machine I have available is an OpenVPN

Re: EOL problems in cvs2svn converted repository

2018-02-10 Thread Ryan Schmidt
On Feb 10, 2018, at 09:29, Bo Berglund wrote: > I tried the contrib py script on my Windows machine as follows: > > python svn_apply_autoprops.py --config %APPDATA%\Subversion\config > D:\Engineering\Projects\Subversion\EI > Traceback (most recent call last): > File "svn_apply_autoprops.py",

Re: EOL problems in cvs2svn converted repository

2018-02-10 Thread Bo Berglund
On Fri, 9 Feb 2018 14:06:33 -0600, Ryan Schmidt wrote: >If you want to do it after the conversion by just setting the >property starting now, without altering history, then check out >a working copy, set the properties where you want them, then check it in. I

Re: EOL problems in cvs2svn converted repository

2018-02-09 Thread Ryan Schmidt
On Feb 9, 2018, at 14:48, Johan Corveleyn wrote: > ISTR there used to be a helper script to do this (to apply a certain > autoprops configuration to your working copy ... > svn-apply-autoprops.py or .pl or something), but I can't find it. > Maybe it was in the contrib folder which has been

Re: EOL problems in cvs2svn converted repository

2018-02-09 Thread Ryan Schmidt
On Feb 9, 2018, at 13:04, Bo Berglund wrote: > OK, I think I will be OK with only setting the trunk version files > correctly, if possible. After all this is what the consultants will > use. > And the development IDE:s seem to be able to cope fine with UNIX style > source files (at least those I

Re: EOL problems in cvs2svn converted repository

2018-02-09 Thread Johan Corveleyn
On Fri, Feb 9, 2018 at 8:04 PM, Bo Berglund wrote: > On Fri, 9 Feb 2018 13:40:43 +0100, Johan Corveleyn > wrote: > >>> We use VisualSVN with svn version 1.9.7 on the server >> >>Standard dump/load cannot do this. >> >>However, you might be able to do it

Re: EOL problems in cvs2svn converted repository

2018-02-09 Thread Ryan Schmidt
On Feb 9, 2018, at 04:44, Bo Berglund wrote: > On Thu, 11 Jan 2018 09:51:54 -0600, Ryan Schmidt wrote: > >>> I found a section in the conf file named [auto-props] but it seems >>> only to be applicable for commit and import, not for checkout AFAICT. >>> And all of that section is commented out

Re: EOL problems in cvs2svn converted repository

2018-02-09 Thread Bo Berglund
On Fri, 9 Feb 2018 13:40:43 +0100, Johan Corveleyn wrote: >> We use VisualSVN with svn version 1.9.7 on the server > >Standard dump/load cannot do this. > >However, you might be able to do it using this tool: >https://github.com/jwiegley/svndumptool > >(it can manipulate dump

Re: EOL problems in cvs2svn converted repository

2018-02-09 Thread Daniel Shahaf
Johan Corveleyn wrote on Fri, 09 Feb 2018 13:40 +0100: > So changing this in historic revisions (in a dump file) is not just a > question of adding the property, it also involves normalizing the > corresponding file contents in the dump (and the dump format contains > checksums and offsets, so

Re: EOL problems in cvs2svn converted repository

2018-02-09 Thread Bo Berglund
On Thu, 11 Jan 2018 09:51:54 -0600, Ryan Schmidt wrote: >> I found a section in the conf file named [auto-props] but it seems >> only to be applicable for commit and import, not for checkout AFAICT. >> And all of that section is commented out by default. > >If you

Re: EOL problems in cvs2svn converted repository

2018-01-11 Thread Ryan Schmidt
On Jan 11, 2018, at 05:43, Bo Berglund wrote: > I have converted our CVS repositories to SVN using cvs2svn.py v 2.5.0. > It looked like it was successful but now when I am working in the > checked out code I noticed that the line endings are UNIX style even > when checking out on Windows (our

EOL problems in cvs2svn converted repository

2018-01-11 Thread Bo Berglund
I have converted our CVS repositories to SVN using cvs2svn.py v 2.5.0. It looked like it was successful but now when I am working in the checked out code I noticed that the line endings are UNIX style even when checking out on Windows (our main working platform). With CVS we always got a