RE: [EXTERNAL] Re: svnsync Error About Disallowed "non-regular" Property

Den fre 16 aug. 2024 kl 18:37 skrev Williams, James P. {Jim} (JSC-CD4)[KBR Wyle Services, LLC] via users mailto:users@subversion.apache.org>>: I sort of did that before posting, but results depend on how and where I ask. # remote host, http:// finds nothing remote-host> svn propget --revpr

Re: [EXTERNAL] Re: svnsync Error About Disallowed "non-regular" Property

Den fre 16 aug. 2024 kl 18:37 skrev Williams, James P. {Jim} (JSC-CD4)[KBR Wyle Services, LLC] via users : > I sort of did that before posting, but results depend on how and where I > ask. > ># remote host, http:// finds nothing >remote-host> svn propget --revprop -r 0 svn:entry:committed-

RE: [EXTERNAL] Re: svnsync Error About Disallowed "non-regular" Property

> From: Andreas Stieger > Sent: Friday, August 16, 2024 4:08 AM > > When I run the following on a number of my SVN repos, > > > >% svnsync initialize file:///my/mirror file:///my/original > > > > I get this error. > > > >svnsync: E165002: Storage of non-regular property > > 'svn:entry:comm

Re: svnsync Error About Disallowed "non-regular" Property

On 2024-08-16 00:58, Williams, James P. {Jim} (JSC-CD4)[KBR Wyle Services, LLC] via users wrote: When I run the following on a number of my SVN repos,    % svnsync initialize file:///my/mirror file:///my/original I get this error.    svnsync: E165002: Storage of non-regular property 'svn:en

Re: svnsync on SVNParentPath

Den mån 21 nov. 2022 kl 12:02 skrev Andreas Stieger : > Hi, > > > Is it possible to setup svnsync from an SVNParentPath? > > I'd like to avoid reconfiguring the mirror every time a new repository > is created. > > No, needs some mild scripting, also to put in place the hooks for each > repo. > Th

Re: svnsync on SVNParentPath

Hi, > Is it possible to setup svnsync from an SVNParentPath? > I'd like to avoid reconfiguring the mirror every time a new repository is > created. No, needs some mild scripting, also to put in place the hooks for each repo. Andreas    

Re: svnsync: E120106: ra_serf: The server sent a truncated HTTP response body.

On Tue, Nov 15, 2022 at 3:56 PM JITHIN K wrote: > > @pavel.lyalya...@visualsvn.com > > This works for me. Thank you. > > Regards, > Jithin K Sure thing! I'm glad that helped you out. On Tue, Nov 15, 2022 at 3:56 PM JITHIN K wrote: > > @pavel.lyalya...@visualsvn.com > > This works for me. Thank

Re: svnsync: E120106: ra_serf: The server sent a truncated HTTP response body.

@pavel.lyalya...@visualsvn.com This works for me. Thank you. Regards, Jithin K On Tue, Nov 15, 2022 at 2:29 PM JITHIN K wrote: > Thanks for your mail. I will try this option. > > > On Mon, Nov 14, 2022 at 8:59 PM Pavel Lyalyakin < > pavel.lyalya...@visualsvn.com> wrote: > >> On Mon, Nov 14, 20

Re: svnsync: E120106: ra_serf: The server sent a truncated HTTP response body.

Thanks for your mail. I will try this option. On Mon, Nov 14, 2022 at 8:59 PM Pavel Lyalyakin < pavel.lyalya...@visualsvn.com> wrote: > On Mon, Nov 14, 2022 at 4:31 PM JITHIN K wrote: > > > > Hello Team, > > > > I use Subversion 1.13 in Ubuntu 20.04.5 LTS and sync a repository size > of 300GB t

Re: svnsync: E120106: ra_serf: The server sent a truncated HTTP response body.

Thanks for your response. I have checked the revision size which is around 2.5GB. I don't think its a revision size problem. On Mon, Nov 14, 2022 at 7:29 PM Daniel Sahlberg wrote: > Den mån 14 nov. 2022 kl 13:31 skrev JITHIN K : > >> Hello Team, >> >> I use Subversion 1.13 in Ubuntu 20.04.5 LTS

Re: svnsync: E120106: ra_serf: The server sent a truncated HTTP response body.

On Mon, Nov 14, 2022 at 4:31 PM JITHIN K wrote: > > Hello Team, > > I use Subversion 1.13 in Ubuntu 20.04.5 LTS and sync a repository size of > 300GB to a mirror server ( same version of SVN and OS ). > > I get the following warning svnsync: E120106: ra_serf: The server sent a > truncated HTTP r

Re: [External] : Re: svnsync: E120106: ra_serf: The server sent a truncated HTTP response body.

I have seen this sort of thing, and I think the cause is that it is taking SVN a long time to put together the transaction and, during that time, no data is going through the HTTP pipe and the connection times out.  I am pretty sure the Apache setting to change here is "Timeout". On 11/14/2022

Re: svnsync: E120106: ra_serf: The server sent a truncated HTTP response body.

Den mån 14 nov. 2022 kl 13:31 skrev JITHIN K : > Hello Team, > > I use Subversion 1.13 in Ubuntu 20.04.5 LTS and sync a repository size of > 300GB to a mirror server ( same version of SVN and OS ). > > I get the following warning svnsync: E120106: ra_serf: The server sent a > truncated HTTP respon

Re: svnsync and commit metadata

James Stocks wrote on Thu, 10 Sep 2020 15:01 +0100: > [...], this wrongly asserts that the mirror is out of > sync during the brief window when the mirror hasn't caught up. > > We would like to find a way of inspecting the time of a given commit > being successfully synchronised to a mirror as opp

Re: SVNSYNC issue with user

Andreas Stieger wrote on Fri, 13 Mar 2020 11:45 +00:00: > Hello, >   > > > “svnsync init --allow-non-empty --username abcd file:///u03/svn/repos > > svn://xxx.xxx.xxx.xxx/” > [...] > > svnsync: E165001: Revprop change blocked by pre-revprop-change hook (exit > > code 1) with output: > > Changing

Re: SVNSYNC issue with user

Hello,   > “svnsync init --allow-non-empty --username abcd file:///u03/svn/repos > svn://xxx.xxx.xxx.xxx/” [...] > svnsync: E165001: Revprop change blocked by pre-revprop-change hook (exit > code 1) with output: > Changing revision properties is not permitted, the user used is klnm When running

RE: Svnsync with changed url and ssl certificate?

On Sun, 11 Aug 2019 22:21:24 -0500, Ryan Schmidt wrote: >> svnsync synchronize https://svn..com/svn/bosse >> https://engineering/svn/bosse >> svnsync: E175008: While handling the 'svn:sync-lock' property on >> '/svn/bosse/!svn/bln/0': >> svnsync: E175008: Revprop change blocked by pre-

Re: Svnsync with changed url and ssl certificate?

On Aug 11, 2019, at 03:30, Bo Berglund wrote: > H:\>svnsync synchronize https://svn..com/svn/bosse > https://engineering/svn/bosse > Authentication realm: Subversion Repository > Password for 'Bosse': * > Authentication realm:

RE: Svnsync with changed url and ssl certificate?

On Thu, 8 Aug 2019 23:12:22 +0200, "Bo Berglund" wrote: >> Subversion keeps track of repository identities not using URLs (since URLs >> can change, and since >> you could even have multiple URLs that refer to a single repository) but >> using UUIDs which are >> assigned at repository creation

RE: Svnsync with changed url and ssl certificate?

-Original Message- From: Ryan Schmidt [mailto:subversion-2...@ryandesign.com] Sent: den 8 augusti 2019 19:25 To: Bo Berglund Cc: Subversion Users Subject: Re: Svnsync with changed url and ssl certificate? >> On Aug 7, 2019, at 00:52, Bo Berglund wrote: >> >> I have

Re: Svnsync with changed url and ssl certificate?

On Aug 7, 2019, at 00:52, Bo Berglund wrote: > I have a svn 1.9.7 system to maintain. > The main server (on Windows Server 2016) is backed up using svnsync over the > Internet to a backup server set up on Ubuntu Server 18 LTS. > The backups are done using a batch file running once every night

Re: svnsync: E175002: REPORT request on '//!svn/rev/' failed

Nick Burkitt wrote on Fri, 28 Dec 2018 10:19 -0800: > I contacted CollabNet, and while they didn't find a solution to the > svnsync problem per se, they did provide instructions for creating a > local backup using "snvrdump dump" and "svnadmin load." Interesting. 'svnrdump dump' and 'svnsync sy

RE: svnsync: E175002: REPORT request on '//!svn/rev/' failed

- From: Daniel Shahaf [mailto:d...@daniel.shahaf.name] Sent: Monday, 17 December, 2018 01:56 To: Nick Burkitt ; users@subversion.apache.org Subject: Re: svnsync: E175002: REPORT request on '//!svn/rev/' failed Nick Burkitt wrote on Fri, 14 Dec 2018 12:36 -0800: > The operation proc

RE: svnsync: E175002: REPORT request on '//!svn/rev/' failed

shahaf.name] Sent: Monday, 17 December, 2018 01:56 To: Nick Burkitt ; users@subversion.apache.org Subject: Re: svnsync: E175002: REPORT request on '//!svn/rev/' failed Nick Burkitt wrote on Fri, 14 Dec 2018 12:36 -0800: > The operation proceeds without problems until it gets to re

Re: svnsync: E175002: REPORT request on '//!svn/rev/' failed

Nick Burkitt wrote on Fri, 14 Dec 2018 12:36 -0800: > Committed revision 69. > Copied properties for revision 69. > Transmitting file data ... > Committed revision 70. > Copied properties for revision 70. > svnsync: E175002: REPORT request on '//!svn/rev/71' failed > PS E:\svn> > ==

Re: svnsync: E175002: REPORT request on '//!svn/rev/' failed

Nick Burkitt wrote on Fri, 14 Dec 2018 12:36 -0800: > The operation proceeds without problems until it gets to revision 71, at > which point it fails with the error "svnsync: E175002: REPORT request on > '//!svn/rev/71' failed". I've looked at all the related answers I > could find, but none of the

Re: svnsync fails to replicate large revision

On Fri, 13 Jul 2018 20:01:13 +, Colin Foster wrote: >I'm not sure if this is a "bug", a "configuration issue", or simply a network >issue. FWIW: Back in March I set up a svnsync replication of our main SVN repository (which is on Windows Server 16 with SVN 1.9.7) across the Internet. I als

Re: SVNSYNC questions

Please consider stopping to top-post. On 05/02/2018 10:43 PM, Paul Greene wrote: > Ok, thanks, I was hoping I wouldn't have to manually create 110 > folders and set permissions, but it is what it is. Is that not something what a shell is usually happy to do for you in a loop? Anyway, as you may

Re: SVNSYNC questions

On Wed, May 2, 2018 at 5:13 PM, Bo Berglund wrote: > On Wed, 2 May 2018 16:43:06 -0400, Paul Greene > wrote: > >>Ok, thanks, I was hoping I wouldn't have to manually create 110 folders and >>set permissions, but it is what it is. > > And additionally since you have 110 repositories you need to ru

Re: SVNSYNC questions

On Wed, 2 May 2018 16:43:06 -0400, Paul Greene wrote: >Ok, thanks, I was hoping I wouldn't have to manually create 110 folders and >set permissions, but it is what it is. And additionally since you have 110 repositories you need to run svnsync against each of these every time you want the sync t

Re: SVNSYNC questions

Ok, thanks, I was hoping I wouldn't have to manually create 110 folders and set permissions, but it is what it is. On Wed, May 2, 2018 at 4:40 PM, Geoff Rowell wrote: > 1. Create the destination repositories. > 2. Configure the destination repository access rights. > 3. Use "svnsync init" on eac

Re: SVNSYNC questions

1. Create the destination repositories. 2. Configure the destination repository access rights. 3. Use "svnsync init" on each destination repository. 4. Run "svnsync sync" on each to copy content. On Wed, May 2, 2018 at 4:16 PM, Paul Greene wrote: > /data/subversion *contains* the repositories -

Re: SVNSYNC questions

/data/subversion *contains* the repositories - it is not a repository itself. So, will the /data/subversion/repo01, /data/subversion/repo02, ... /data/subversion/repo110 automatically be created, or do I have to make them myself? On Wed, May 2, 2018 at 4:09 PM, Andreas Stieger wrote: > Hello, >

Re: SVNSYNC questions

Hello, On 05/02/2018 10:02 PM, Paul Greene wrote: > Prior to running svnsync, do I need to create the same folder > structure on the destination as on the source? no, just an empty, randomly named repository. > i.e. the source has 110 repositories located under /data/subversion. I > have a fold

Re: svnsync: E210008: Error while replaying commit

On Mon, Sep 18, 2017 at 9:43 AM, Dummy <3295285...@qq.com> wrote: > hi, > Here comes a error when i exec svnsync to mirror a repo: > svnsync: E210008: Error while replaying commit > the sync user has the full access,i do not know why,any suggestion for me > please? or is there any details error log

Re: svnsync size differences

  > i svnsync gzrepos(centos 6.4-svn1.6.11) to gz-mirror1(centos 7-svn1.9.5), > [...] > mirror repo(gz-mirror1) is more less than source repo(gzrepos) in sizes > the source repo(gzrepos) is 177G while the mirror one(gz-mirror1)  is only 66G > for example: revision:2012,it seems to be compressed P

Re: svnsync on large files

Hello Daniel, On Thu, Dec 8, 2016 at 1:08 AM, Daniel Shahaf wrote: > > Pavel Lyalyakin wrote on Wed, Dec 07, 2016 at 20:59:24 +0300: > > On Wed, Dec 7, 2016 at 8:54 PM, Stümpfig, Thomas > > wrote: > > > > > > The rev to be synced is 2,291,973,385 Bytes large (Size in txn-protorevs > > > directo

svnsync: fewer round-trips for small revisions (was: Re: svnsync on large files)

Daniel Shahaf wrote on Thu, Dec 08, 2016 at 06:20:20 +: > The steps should be this: > > f() { > token="$USER@$(hostname):${RANDOM}:${RANDOM}" > svn propset --revprop -r0 -- svn:sync-lock $token > svn propget --revprop -r0 --strict svn:sync-lock | fgrep -q -- $token || > return 1 > svn

Re: svnsync on large files

Stümpfig, Thomas wrote on Thu, Dec 08, 2016 at 07:36:10 +: > Hi Daniel, > you are a guru. I don't know why but it worked! > > I guess the magic is in the difference of network transmission of svnsync vs > svnrdump / svnadmin load That's pretty unlikely: svnsync and svnrdump use the very same

RE: svnsync on large files

homas -Original Message- From: Daniel Shahaf [mailto:danie...@apache.org] Sent: Donnerstag, 8. Dezember 2016 07:20 To: Stümpfig, Thomas (DF PL S&SE DE PSM EAI) Cc: Pavel Lyalyakin ; users@subversion.apache.org Subject: Re: svnsync on large files Stümpfig, Thomas wrote on Wed, Dec 07, 2016 at

Re: svnsync on large files

Stümpfig, Thomas wrote on Wed, Dec 07, 2016 at 23:32:38 +: > This is the situation of the starting point. (I restored) The steps should be this: f() { token="$USER@$(hostname):${RANDOM}:${RANDOM}" svn propset --revprop -r0 -- svn:sync-lock $token svn propget --revprop -r0 --strict svn:s

RE: svnsync on large files

To: Stümpfig, Thomas (DF PL S&SE DE PSM EAI) ; users@subversion.apache.org Subject: Re: svnsync on large files Hello Thomas, On Wed, Dec 7, 2016 at 8:54 PM, Stümpfig, Thomas wrote: > > Hi everybody, > > i get an error with svnsync for large files. svnsync: E175002: REPORT &

RE: svnsync on large files

l Lyalyakin Cc: Stümpfig, Thomas (DF PL S&SE DE PSM EAI) ; users@subversion.apache.org Subject: Re: svnsync on large files Pavel Lyalyakin wrote on Wed, Dec 07, 2016 at 20:59:24 +0300: > On Wed, Dec 7, 2016 at 8:54 PM, Stümpfig, Thomas > wrote: > > > > The rev to be synce

Re: svnsync on large files

Pavel Lyalyakin wrote on Wed, Dec 07, 2016 at 20:59:24 +0300: > On Wed, Dec 7, 2016 at 8:54 PM, Stümpfig, Thomas > wrote: > > > > The rev to be synced is 2,291,973,385 Bytes large (Size in txn-protorevs > > directory. Of target mirror) > > > > The sync is with svn 1.9.5 (Visual SVN Server) over b

Re: svnsync on large files

Hello Thomas, On Wed, Dec 7, 2016 at 8:54 PM, Stümpfig, Thomas wrote: > > Hi everybody, > > i get an error with svnsync for large files. svnsync: E175002: REPORT request > on It seems to be only the first part of the error message. What's the full wording of the error? > > The rev to be synce

Re: svnsync error : Error while replaying commit

Hi, you might wanna repost your question in English. I'm not sure whether anybody here can read Chinese (if it is Chinese, that is). All I can make out of this report is that you seem to get some error running svnsync which seems to be a rather old version (1.7.4). If you want/need to stick wi

Re: svnsync error : Error while replaying commit

我也遇到了该问题Error while replaying commit，有些库用下面同样的步骤操作是没问题的，但是有些库就报这个错，不知道为什么，麻烦大家遇到过解决了的回答下，谢谢 我的操作步骤是 1、将脚本aapost-commit.bat放置到SVN主服务器相对应项目的hooks文件里， 例如：\\192.168.27.1\d$\SVN\c3m-video\hooks "C:\Program Files (x86)\Subversion\bin\svnsync.exe" sync --non-interactive svn://192.168.27.88/c3m-video --us

RE: svnsync: Authorization failed

, Hubert Cc: users@subversion.apache.org Subject: Re: svnsync: Authorization failed Hi Hubert, There should be two sets of credentials you can pass to svnsync. I don't remember what they're called for 1.6. Did you try passing the --sync-username and --sync-password? Eric. On Sun, Sep 13,

Re: svnsync: Authorization failed

ptember 14, 2015 2:43 PM > *To:* Li, Hubert > *Cc:* users@subversion.apache.org > *Subject:* Re: svnsync: Authorization failed > > > > Two quick thoughts (I'm not a developer, just a user of Subversion): > > > > 1) 1.6.6 is old. If you can upgrade, you might get easier to unde

Re: svnsync: Authorization failed

ed Thanks, Hubert Li ARRIS *From:*Li, Hubert *Sent:* Monday, September 14, 2015 3:00 PM *To:* 'Eric Johnson' *Cc:* users@subversion.apache.org *Subject:* RE: svnsync: Authorization failed Thanks, Eric. I tried to add –username and –password in svnsync, and got the same error message

RE: svnsync: Authorization failed

, Hubert Li ARRIS From: Li, Hubert Sent: Monday, September 14, 2015 3:00 PM To: 'Eric Johnson' Cc: users@subversion.apache.org Subject: RE: svnsync: Authorization failed Thanks, Eric. I tried to add –username and –password in svnsync, and got the same error messages. Yes, 1.6.6 is old, b

RE: svnsync: Authorization failed

@subversion.apache.org Subject: Re: svnsync: Authorization failed Two quick thoughts (I'm not a developer, just a user of Subversion): 1) 1.6.6 is old. If you can upgrade, you might get easier to understand error messages. 2) The sync operation is trying to sync from some other place. Given that

Re: svnsync: Authorization failed

Two quick thoughts (I'm not a developer, just a user of Subversion): 1) 1.6.6 is old. If you can upgrade, you might get easier to understand error messages. 2) The sync operation is trying to sync *from* some other place. Given that your credentials to access the zch124... repository may be fine,

RE: svnsync: E160016: Path ... not present

> -Original Message- > From: Andrew Reedick [mailto:jreed...@incomm.com] > Sent: Friday, April 24, 2015 1:26 PM > To: users@subversion.apache.org > Subject: svnsync: E160016: Path ... not present > > Anyone familiar with this svnsync bug/issue? I didn't see anything > substantive via go

Re: svnsync problems

On 02/20/15 10:21, Philip Martin wrote: You are making things very hard for yourself by running 1.6.11, it is very old and no longer maintained, unless your distribution is backporting fixes. A newer version will have fewer bugs and better performance. You'll get no disagreement from me on tha

Re: svnsync problems

> On Feb 20, 2015, at 8:21, Branko Čibej wrote: > >> On 20.02.2015 13:59, Nico Kadel-Garcia wrote: >> On Fri, Feb 20, 2015 at 5:50 AM, Philip Martin >> wrote: >>> "Andreas Stieger" writes: >>> In addition to what Philip wrote, for initializing a sync to a target created via hotcopy

Re: svnsync problems

On 20.02.2015 13:59, Nico Kadel-Garcia wrote: > On Fri, Feb 20, 2015 at 5:50 AM, Philip Martin > wrote: >> "Andreas Stieger" writes: >> >>> In addition to what Philip wrote, for initializing a sync to a target >>> created via hotcopy, you will find "svnsync init --allow-non-empty" >>> very useful

Re: svnsync problems

On Fri, Feb 20, 2015 at 5:50 AM, Philip Martin wrote: > "Andreas Stieger" writes: > >> In addition to what Philip wrote, for initializing a sync to a target >> created via hotcopy, you will find "svnsync init --allow-non-empty" >> very useful. > > But only after upgrading as that is not present i

Re: svnsync problems

"Andreas Stieger" writes: > In addition to what Philip wrote, for initializing a sync to a target > created via hotcopy, you will find "svnsync init --allow-non-empty" > very useful. But only after upgrading as that is not present in 1.6. -- Philip Martin | Subversion Committer WANdisco // *No

Re: svnsync problems

> Tony Sweeney writes: > > running under Apache. I set the svn:sync-last-merged-rev revprop on > > r0 to reflect the newest revision on the hotcopy. In addition to what Philip wrote, for initializing a sync to a target created via hotcopy, you will find "svnsync init --allow-non-empty" very u

Re: svnsync problems

You are making things very hard for yourself by running 1.6.11, it is very old and no longer maintained, unless your distribution is backporting fixes. A newer version will have fewer bugs and better performance. 1.6 has a hotcopy bug http://subversion.tigris.org/issues/show_bug.cgi?id=3596 t

Re: SVNSYNC

"Somashekarappa, Anup (CWM-NR)" writes: > So I tried to change the url to ne url in Repository/db/revprops/0/0 > (in the unix server ) You should use svn to change the r0 revision properties, typically with a file:/// URL to the destination repository: svn proplist -v --revprop -r0 file:///...

Re: SVNSYNC

On Fri, Jan 16, 2015 at 5:07 AM, Somashekarappa, Anup (CWM-NR) wrote: > > > Hi, > > We do have Master- Slave set up and slave has been initialized to Master > url. > > Master Url : http://svnserver.com:8080/svn > Slave Url : http://svnSlave.com:8080/svn > > We have synced master and slave using th

Re: svnsync/diff zlib - trying to understand/figure out an error

Hello, On 11/12/2014 14:06, Marc Verwerft wrote: While creating a replica of an existing repository using svnsync, I bumped into a problem that I'm trying to figure out. In short, I don't think SVN is to blame but that we've got a corrupted transaction/file somewhere. I'm just trying to figure

Re: svnsync via svn+ssh w/key authentication: password prompt

"Sampson, Barry" writes: > Using svn, I can do this without being prompted for a password: > svn list svn+ssh://servername/path/to/repos > > However, this does prompt for a password: > svnsync sync svn+ssh://servername/path/to/repos > > And just for good measure, this does the same thing: > svnsy

RE: svnsync via svn+ssh w/key authentication: password prompt

@subversion.apache.org Subject: Re: svnsync via svn+ssh w/key authentication: password prompt On 29 Aug 2014, at 17:22, "Sampson, Barry" mailto:barry.samp...@teejet.com>> wrote: I am attempting to use svnsync over a SSH tunnel, which works, but always prompts for a password. I alrea

Re: svnsync via svn+ssh w/key authentication: password prompt

On Fri, Aug 29, 2014 at 12:22 PM, Sampson, Barry wrote: > I am attempting to use svnsync over a SSH tunnel, which works, but always > prompts for a password. I already setup ssh key authentication, which does > work fine when performing svn commands. Ahh. Welcome to the world of "ssh-agent', and

Re: svnsync via svn+ssh w/key authentication: password prompt

> On 29 Aug 2014, at 17:22, "Sampson, Barry" wrote: > > I am attempting to use svnsync over a SSH tunnel, which works, but always > prompts for a password. I already setup ssh key authentication, which does > work fine when performing svn commands. > > I can establish a SSH tunnel with key

Re: svnsync sync error parsing arguments

On Tue, Feb 25, 2014 at 5:34 PM, Thorsten Schöning wrote: > Guten Tag Joel Rees, > am Montag, 24. Februar 2014 um 23:47 schrieben Sie: > >> --- >> $ svnsync sync https://svn.sourceforge.jp/svnroot/bif-c/ >> https://svn.code.sf.net/p/bif-c --username reiisi >> svnsync: より詳しく知りたいときは 'svn

Re: svnsync sync error parsing arguments

Guten Tag Joel Rees, am Montag, 24. Februar 2014 um 23:47 schrieben Sie: > --- > $ svnsync sync https://svn.sourceforge.jp/svnroot/bif-c/ > https://svn.code.sf.net/p/bif-c --username reiisi > svnsync: より詳しく知りたいときは 'svnsync help' を試してみてください > svnsync: 引数をパースする際にエラーが生じました > -

Re: svnsync sync error parsing arguments

On Mon, Feb 24, 2014 at 11:42 PM, Philip Martin wrote: > Joel Rees writes: > >> On Mon, Feb 24, 2014 at 10:14 PM, Philip Martin >>> >>> You are probably using Subversion 1.6 which doesn't support the optional >>> source URL parameter. >> >> That would make sense, except that when I initialized th

Re: svnsync sync error parsing arguments

Joel Rees writes: > On Mon, Feb 24, 2014 at 10:14 PM, Philip Martin >> >> You are probably using Subversion 1.6 which doesn't support the optional >> source URL parameter. > > That would make sense, except that when I initialized the mirror, I > used the source and sync arguments and it didn't co

Re: svnsync sync error parsing arguments

On Mon, Feb 24, 2014 at 10:14 PM, Philip Martin wrote: > Joel Rees writes: > >> $svnsync sync https://svn.sourceforge.jp/svnroot/bif-c/ >> https://svn.code.sf.net/p/bif-c/code --sync-username reiisi >> --source-username reiisi >> svnsync: より詳しく知りたいときは 'svnsync help' を試してみてください >> [For details abo

Re: svnsync sync error parsing arguments

Philip Martin writes: > Joel Rees writes: > >> $svnsync sync https://svn.sourceforge.jp/svnroot/bif-c/ >> https://svn.code.sf.net/p/bif-c/code --sync-username reiisi >> --source-username reiisi >> svnsync: より詳しく知りたいときは 'svnsync help' を試してみてください >> [For details about svnsync, try svnsync help.] >

Re: svnsync sync error parsing arguments

Joel Rees writes: > $svnsync sync https://svn.sourceforge.jp/svnroot/bif-c/ > https://svn.code.sf.net/p/bif-c/code --sync-username reiisi > --source-username reiisi > svnsync: より詳しく知りたいときは 'svnsync help' を試してみてください > [For details about svnsync, try svnsync help.] > svnsync: 引数をパースする際にエラーが生じました >

Re: svnsync: properties not always copied?

Dustin Lang writes: > (Patch: > http://astrometry.net/svn/trunk/scripts/svnsync/sort-dels.diff, but I > don't know if it still applies or is needed) A similar fix is on trunk, 1.8 and 1.7. -- Philip Martin | Subversion Committer WANdisco // *Non-Stop Data*

Re: svnsync: properties not always copied?

Hi Mark, I do not want to sidetrack this discussion and it sounds like you are not having the issue I am going to mention, but I thought you could not rely on this any more due to the random hash ordering of APR in recent releases (which would yield different md5sum)? At one point I put in

RE: svnsync: properties not always copied?

Dear Bert, Thanks very much for your reply. I was also frustrated that I was not able to create a small test case that reproduces the problem, hence my plea for ideas of what could be triggering the problem. Your example 'svn:mergeinfo' missing could be caused by older Subversion clients t

Re: svnsync: properties not always copied?

On Mon, Nov 18, 2013 at 12:10 PM, Dustin Lang wrote: > I keep an svnsync'd mirror of my svn repository, and I run a very > stringent verification check: I do an "svnadmin dump" on the original and > the mirror, and demand that they have the same md5sum. It is paranoid, but > paranoia is good wh

RE: svnsync: properties not always copied?

> -Original Message- > From: Dustin Lang [mailto:dstnd...@gmail.com] On Behalf Of Dustin Lang > Sent: maandag 18 november 2013 18:10 > To: users@subversion.apache.org > Subject: svnsync: properties not always copied? > > > [I am not on the list; please cc me in replies] > > Hi, > > I ke

Re: svnsync --disable-locking

Seumas Soltysik writes: > I am still a bit confused about the difference between --steal-lock and > --disable-locking. I understand that --steal-lock basically deletes/steals > the lock property on revision 0 which controls who has the right to perform > an svnsync. I use this in the event that a

Re: svnsync --disable-locking

Phillip, Thanks for the reply. I was hoping it would allow me to sync without regard file locks. In the end I just used rmlocks to remove the lock and then re-ran svnsync. I am still a bit confused about the difference between --steal-lock and --disable-locking. I understand that --steal-lock basi

Re: svnsync --disable-locking

Seumas Soltysik writes: > I am using svnsync to sync a mirror with a master. However, I am getting > the following error: > svnsync: E160039: User '' does not own lock on path '/foo/bar' > > I understand why this is happening but I am not sure what the solution is. > > Based upon the svnsync

Re: svnsync crashes on a huge commit

Hi Anatoly, can you build a custom version of the serf library used by your svn client to enable logging? Attached patch should enable the logging needed, I hope it should clarify the original " internal malfunction" error you reported earlier. You can send the log output to me privately, probab

Re: svnsync crashes on a huge commit

On Thu, Jul 11, 2013 at 02:04:11PM +0400, Anatoly Zapadinsky wrote: > I've increased swap size to 8gb, increased opened files handles limit to > 200k and ran the process at night when the server is not very busy. > > Finally svnsync form a revision copy in db, but hang after it. It didn't > print

Re: svnsync crashes on a huge commit

I've increased swap size to 8gb, increased opened files handles limit to 200k and ran the process at night when the server is not very busy. Finally svnsync form a revision copy in db, but hang after it. It didn't print "Committed revision" just hanged on a set of dots after "Transmitting file dat

RE: svnsync crashes on a huge commit

e with the VIP having a time out at 2 minutes. We had to increase that temporarily to accommodate some very large commits. Cheers, Thomas From: Anatoly Zapadinsky [mailto:zapadin...@gmail.com] Sent: Tuesday, July 09, 2013 1:48 PM To: Anatoly Zapadinsky; users@subversion.apache.org Subject: R

Re: svnsync crashes on a huge commit

it's very unlikely to be a memory leak... svnsync worked for 20+ hours and synchronized 300 000+ revisions and downloaded 65+ Gb during the one sync session before it felt in this trap. now it stuck... and can't synchronize this revision after restart. The procedure is very slow, it took more than

Re: svnsync crashes on a huge commit

Stefan Sperling wrote on Tue, Jul 09, 2013 at 19:13:32 +0200: > On Tue, Jul 09, 2013 at 03:30:44PM +0400, Anatoly Zapadinsky wrote: > > svnsync failed to sync repository with a single commit containing 56000 > > files. This commit handled perfectly by console svn and tortoise svn. We > > can checko

Re: svnsync crashes on a huge commit

On Tue, Jul 09, 2013 at 03:30:44PM +0400, Anatoly Zapadinsky wrote: > svnsync failed to sync repository with a single commit containing 56000 > files. This commit handled perfectly by console svn and tortoise svn. We > can checkout this folder structure and so on. But when I tried to sync this > co

Re: svnsync 1.8.0 fails if htdigest authentication is used

he > >> next serf release. (Which should happen with or before Subversion > 1.8.1). > >> > >> > >> > >> Bert > >> > >> > >> > >> [Added CC to one of the serf developers, who isn’t subscribed to t

Re: svnsync 1.8.0 fails if htdigest authentication is used

. >> >> >> >> Bert >> >> >> >> [Added CC to one of the serf developers, who isn’t subscribed to this >> list] >> >> >> >> From: Vadym Chepkov [mailto:vchep...@gmail.com] >> Sent: maandag 1 jul

Re: svnsync 1.8.0 fails if htdigest authentication is used

rs, who isn’t subscribed to this list] > > > ** ** > > *From:* Vadym Chepkov [mailto:vchep...@gmail.com] > *Sent:* maandag 1 juli 2013 18:32 > *To:* Bert Huijben > *Cc:* users@subversion.apache.org; Ryan Schmidt > > *Subject:* Re: svnsync 1.8.0 fails if htdigest authenticatio

RE: svnsync 1.8.0 fails if htdigest authentication is used

f the serf developers, who isn't subscribed to this list] From: Vadym Chepkov [mailto:vchep...@gmail.com] Sent: maandag 1 juli 2013 18:32 To: Bert Huijben Cc: users@subversion.apache.org; Ryan Schmidt Subject: Re: svnsync 1.8.0 fails if htdigest authentication is used Bert, I wo

Re: svnsync 1.8.0 fails if htdigest authentication is used

/!svn/rev/0': could not connect to server (http://example.com) Regards, Vadym On Mon, Jul 1, 2013 at 12:07 PM, Bert Huijben wrote: > > > > -Original Message- > > From: Vadym Chepkov [mailto:vchep...@gmail.com] > > Sent: zondag 30 juni 2013 22:58 > > To: R

RE: svnsync 1.8.0 fails if htdigest authentication is used

> -Original Message- > From: Vadym Chepkov [mailto:vchep...@gmail.com] > Sent: zondag 30 juni 2013 22:58 > To: Ryan Schmidt > Cc: users@subversion.apache.org > Subject: Re: svnsync 1.8.0 fails if htdigest authentication is used > > > On Jun 30, 2013, at

Re: svnsync 1.8.0 fails if htdigest authentication is used

On Jun 30, 2013, at 2:18 PM, Ryan Schmidt wrote: > > On Jun 30, 2013, at 07:06, Vadym Chepkov wrote: > >> After I upgraded to 1.8.0, svnsync process started to fail. I am using >> apache 2.2.3. I suspect it's really serf's problem (1.2.1), but nevertheless >> I had to revert back to 1.7.10. I

Re: svnsync 1.8.0 fails if htdigest authentication is used

On Jun 30, 2013, at 07:06, Vadym Chepkov wrote: > After I upgraded to 1.8.0, svnsync process started to fail. I am using apache > 2.2.3. I suspect it's really serf's problem (1.2.1), but nevertheless I had > to revert back to 1.7.10. Is this a known limitation? You said you upgraded to 1.8.0.

Re: svnsync 1.8.0 fails if there is a non-printable characters in the commit message

On 2013-06-26 01:05, Daniel Shahaf wrote: > olli hauer wrote on Tue, Jun 25, 2013 at 17:06:35 +0200: >> On 2013-06-25 16:02, Daniel Shahaf wrote: >>> Daniel Shahaf wrote on Tue, Jun 25, 2013 at 16:55:24 +0300: Daniel Shahaf wrote on Tue, Jun 25, 2013 at 13:50:58 +: > On Mon, Jun 24, 20

Re: svnsync 1.8.0 fails if there is a non-printable characters in the commit message

olli hauer wrote on Tue, Jun 25, 2013 at 17:06:35 +0200: > On 2013-06-25 16:02, Daniel Shahaf wrote: > > Daniel Shahaf wrote on Tue, Jun 25, 2013 at 16:55:24 +0300: > >> Daniel Shahaf wrote on Tue, Jun 25, 2013 at 13:50:58 +: > >>> On Mon, Jun 24, 2013 at 09:47:17PM +0200, Ben Smith-Mannschott

  1   2   3   4   >