Re: Migrating old format repositories (format 4), running into bad line endings

Thanks for the reply. On 8/22/16 5:25 PM, Daniel Shahaf wrote: Eric Johnson wrote on Mon, Aug 22, 2016 at 14:29:47 -0700: * // move original repo out of the way, move new copy into position. At the comma you should restart the server to flush caches: http://mail-archives.apache.org/mo

Re: Migrating old format repositories (format 4), running into bad line endings

Eric Johnson wrote on Mon, Aug 22, 2016 at 14:29:47 -0700: > * // move original repo out of the way, move new copy into position. At the comma you should restart the server to flush caches: http://mail-archives.apache.org/mod_mbox/subversion-users/201606.mbox/%3c20160609125706.GA4020@tarsus

Re: Migrating old format repositories (format 4), running into bad line endings

On Mon, Aug 22, 2016 at 5:29 PM, Eric Johnson wrote: > Hi Mark, > > On 8/22/16 2:06 PM, Mark Phippard wrote: > >> On Mon, Aug 22, 2016 at 2:11 PM, Eric Johnson > e...@tibco.com>> wrote: >> >> So I wrote myself a tool to go through all commit comments, and >> verify that no "CRs" appear in

Re: Migrating old format repositories (format 4), running into bad line endings

Hi Mark, On 8/22/16 2:06 PM, Mark Phippard wrote: On Mon, Aug 22, 2016 at 2:11 PM, Eric Johnson > wrote: So I wrote myself a tool to go through all commit comments, and verify that no "CRs" appear in the svn:log entry. If I find them, I rewrite the log entry.

Re: Migrating old format repositories (format 4), running into bad line endings

Mark Phippard wrote on Mon, Aug 22, 2016 at 17:06:05 -0400: > On Mon, Aug 22, 2016 at 2:11 PM, Eric Johnson wrote: > > > So I wrote myself a tool to go through all commit comments, and verify > > that no "CRs" appear in the svn:log entry. If I find them, I rewrite the > > log entry. That way, I c

Re: Migrating old format repositories (format 4), running into bad line endings

On Mon, Aug 22, 2016 at 2:11 PM, Eric Johnson wrote: > So I wrote myself a tool to go through all commit comments, and verify > that no "CRs" appear in the svn:log entry. If I find them, I rewrite the > log entry. That way, I can clean up existing repositories. > > However, I ran into a surprise.

Re: Migrating old format repositories (format 4), running into bad line endings

Eric Johnson wrote on Mon, Aug 22, 2016 at 11:11:17 -0700: > I've seen that other people recommend editing the dump file directly, but > that makes me quite nervous, especially on an 8MB dump file. Hoping there's > a better way. You could just pass --bypass-prop-validation to 'svnadmin load'. Tha

Migrating old format repositories (format 4), running into bad line endings

So I wrote myself a tool to go through all commit comments, and verify that no "CRs" appear in the svn:log entry. If I find them, I rewrite the log entry. That way, I can clean up existing repositories. However, I ran into a surprise. CR characters have also snuck into the svn:ignore property, whi

Re: "Offset too large" error when packing repository in FSFS 7 format

Thanks Stefan and Daniel for your effort in analyzing this. Unfortunately, I missed your replies as I expected that they will address my mailbox as well. So let me restart the thread now.. Recently I hit this problem on another production repository from one of my customers. My test machine wher

Re: A subersion build environment on CentOS 7.2

On Sun, Aug 21, 2016 at 3:24 PM, Adam Jensen wrote: > On 08/21/2016 07:00 AM, Stefan Sperling wrote: > [snip] >> If your goal is setting up a production environment, I would recommend >> using binary packages system from http://subversion.apache.org/packages.html > > My CentOS (el7.x86_64) machine

Re: A subersion build environment on CentOS 7.2

On Sun, Aug 21, 2016 at 06:02:31PM -0500, horst.schl...@gmx.de wrote: > Yes, this is why I was asking about the errors the makefile is giving. In > the building part of the guide it says > > To start development from scratch, simply download Makefile.svn, create a > symlink called `GNUmakefile` th