You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Gary <li...@yahoo.co.uk> on 2012/03/30 15:25:28 UTC
svnsync: Error while replaying commit
I see a lot of reports of this error, but little in the way of
clear information as to what it might mean, or how to fix it:
$ svnsync sync file://`pwd`/dest
Committed revision 1.
Copied properties for revision 1.
Transmitting file data .....................
[...]
Committed revision 79.
Copied properties for revision 79.
Transmitting file data .......................
Committed revision 80.
Copied properties for revision 80.
svnsync: Error while replaying commit
Huh?
If I look at the source server log, revs 81 & 82 are "missing"
in the trunk. I imagine they are/were in a branch, which AFAIK
is no longer available. Is there any way to get around this?
Assuming that's the problem, of course.
Re: svnsync: Error while replaying commit
Posted by Ulrich Eckhardt <ul...@dominolaser.com>.
Am 02.04.2012 11:39, schrieb Gary:
> See my other email, I got the svn log command wrong, and the branch
> *is* still available, just can't be modified any more. The question
> is, why svnsync gets its knickers into a twist about that. The
> revisions *are* available (and can be checked out, I checked).
Yes, my initial guess was wrong and so you can discard the rest of my
posting that was based on this assumption.
> The "howto" (link in other email) makes no mention of having to do
> anything special to handle repos with branches in a special way.
As far as Subversion itself is concerned, it doesn't even know about
things like branches, they are just copies, so you shouldn't have to do
anything special.
I have no more guesses left what could cause this, good luck!
Uli
**************************************************************************************
Domino Laser GmbH, Fangdieckstra�e 75a, 22547 Hamburg, Deutschland
Gesch�ftsf�hrer: Thorsten F�cking, Amtsgericht Hamburg HR B62 932
**************************************************************************************
Visit our website at http://www.dominolaser.com
**************************************************************************************
Diese E-Mail einschlie�lich s�mtlicher Anh�nge ist nur f�r den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empf�nger sein sollten. Die E-Mail ist in diesem Fall zu l�schen und darf weder gelesen, weitergeleitet, ver�ffentlicht oder anderweitig benutzt werden.
E-Mails k�nnen durch Dritte gelesen werden und Viren sowie nichtautorisierte �nderungen enthalten. Domino Laser GmbH ist f�r diese Folgen nicht verantwortlich.
**************************************************************************************
Re: svnsync: Error while replaying commit
Posted by Gary <li...@yahoo.co.uk>.
From: Ulrich Eckhardt <ul...@dominolaser.com>
>> I imagine they are/were in a branch, which AFAIK is no longer
>> available. Is there any way to get around this? Assuming that's
>> the problem, of course.
>
> Do you know more about this branch and how it was removed? Just "svn
> delete"ing a branch doesn't cause revisions to vanish. I guess the
> repository was modified using the dumpfilter to remove that branch,
> causing a non-contiguous range of revisions. svnsync then chokes on
> this, because it expects the revisions to be contiguous.
See my other email, I got the svn log command wrong, and the branch
*is* still available, just can't be modified any more. The question
is, why svnsync gets its knickers into a twist about that. The
revisions *are* available (and can be checked out, I checked). The
"howto" (link in other email) makes no mention of having to do
anything special to handle repos with branches in a special way.
Re: svnsync: Error while replaying commit
Posted by Ulrich Eckhardt <ul...@dominolaser.com>.
Am 30.03.2012 15:25, schrieb Gary:
> I see a lot of reports of this error, but little in the way of
> clear information as to what it might mean, or how to fix it:
>
> $ svnsync sync file://`pwd`/dest
> Committed revision 1.
> Copied properties for revision 1.
> Transmitting file data .....................
> [...]
> Committed revision 79.
> Copied properties for revision 79.
> Transmitting file data .......................
> Committed revision 80.
> Copied properties for revision 80.
> svnsync: Error while replaying commit
>
> Huh?
>
> If I look at the source server log, revs 81 & 82 are "missing"
> in the trunk.
Just to cut the discussion short here: You used "svn log $REPO_URL"
directly on the root of the repository, not some directory underneath.
Right?
> I imagine they are/were in a branch, which AFAIK is no longer
> available. Is there any way to get around this? Assuming that's
> the problem, of course.
Do you know more about this branch and how it was removed? Just "svn
delete"ing a branch doesn't cause revisions to vanish. I guess the
repository was modified using the dumpfilter to remove that branch,
causing a non-contiguous range of revisions. svnsync then chokes on
this, because it expects the revisions to be contiguous.
This would explain the reasons, but doesn't help you getting the
repository synced. What I would do is this:
1. Try to reproduce this problem in isolation to make sure it is a
problem with dumpfiltered revisions.
2. Try to create empty revisions in the target repository or modify the
last-synced-revision (I believe that svnsync stores such a property
somewhere). The goal is to keep svnsync from trying to sync that
revision from the upstream repository.
3. File an according enhancement request on svnsync.
Uli
**************************************************************************************
Domino Laser GmbH, Fangdieckstra�e 75a, 22547 Hamburg, Deutschland
Gesch�ftsf�hrer: Thorsten F�cking, Amtsgericht Hamburg HR B62 932
**************************************************************************************
Visit our website at http://www.dominolaser.com
**************************************************************************************
Diese E-Mail einschlie�lich s�mtlicher Anh�nge ist nur f�r den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empf�nger sein sollten. Die E-Mail ist in diesem Fall zu l�schen und darf weder gelesen, weitergeleitet, ver�ffentlicht oder anderweitig benutzt werden.
E-Mails k�nnen durch Dritte gelesen werden und Viren sowie nichtautorisierte �nderungen enthalten. Domino Laser GmbH ist f�r diese Folgen nicht verantwortlich.
**************************************************************************************
Re: svnsync: Error while replaying commit
Posted by Gary <li...@yahoo.co.uk>.
----- Original Message -----
From: Giulio Troccoli
>>>>> Why is it showing files in trunk when you're log command is for
>>>>> branches/working ? Or have you just pasted the wrong command?
>>>> Nope, that's the command. I mean, it *is* the log, so... shouldn't it?
>>>> The commands for trunk and branch produce the same output, anyway:
>>>> [12:39:07] jg@ggajg ~/.tmp
>>>> $ svn log -v -r80 svn://devel.<domain>/<repo>/trunk> trunk ; svn log -v -r80 svn://devel.<domain>/<repo>/branches/working> branch
>>>>
>>>> [12:39:26] jg@ggajg ~/.tmp
>>>> $ diff -q trunk branch
>>>>
>>>> [12:39:29] jg@ggajg ~/.tmp
>>>>
>>> What version of SVN are you using? I've got 1.6.12 and if I am in a directory where no changes were made for a revision then svn log doesn't show anything,>e.g.
>>>
>>> svn log -v -r17727
>>> ------------------------------------------------------------------------
>> $ svn --version
>> svn, version 1.6.17 (r1128011)
>> compiled Jun 2 2011, 10:39:28
>>
>> I'm not 100% sure what the server version is.
>>
>>> In the list of files changed in revision 80 that you posted earlier, are there any files at all that are actually in branches/working?
>> No, all are in trunk.
>
>That is really baffling me. But mayber that's because you have different
>version.
Maybe. Don't know.
>I just thought something else. svnsync stops when trying to create the
>branch (rev 81). So maybe the error is something not related to the
>repository, like permission (I don't think so though) or some hooks.
>Sorry, I am a bit to a dead end here.
Not to worry. I appreciate you trying to help. Thank you.
Re: svnsync: Error while replaying commit
Posted by Giulio Troccoli <gi...@mediatelgroup.co.uk>.
On 02/04/12 13:16, Gary wrote:
> ----- Original Message -----
> From: Giulio Troccoli
> On 02/04/12 11:51, Gary wrote:
>> ----- Original Message -----
>> From: Giulio Troccoli
>> On 02/04/12 11:10, Gary wrote:
>>> ----- Original Message -----
>>> From: Giulio Troccoli
>>>> On 02/04/12 10:24, Gary wrote:
>>>>>> that still doesn't explain to me why svnsync barfs on those (not)
>>>>>> missing revisions. Looking at the command line history, I can't see
>>>>>> anywhere where I pointed svnsync at just the trunk, only ever at the
>>>>>> repo/project within the repo (I took my instructions from
>>>>>> http://svn.apache.org/repos/asf/subversion/trunk/notes/svnsync.txt)
>>>>> Well, at least we know that the revisions are not missing.
>>>>>
>>>>> Can you show us the source repository path for you synced repo? It
>>>>> should be in one of the properties stored in revision 0 in the synced
>>>>> repo, if I remember well.
>>>> Do you mean in the properties of the one I am trying to sync into, or
>>>> from?I'm not really sure what you mean :P
>>> Sorry, I wasn't very clear. The one your syncing into, so the
>>> destination repo.
>>> No problem. I don't know if this is exactly what you want, but:
>>> $ cat ./db/revprops/0/0
>>> K 8
>>> svn:date
>>> V 27
>>> 2011-03-01T16:14:38.678110Z
>>> K 17
>>> svn:sync-from-url
>>> V 33
>>> svn://devel.<domain>/<repo>
>>> K 18
>>> svn:sync-from-uuid
>>> V 36
>>> 7c76b8fe-c8ee-45e6-8ede-b17e10a7e991
>>> K 24
>>> svn:sync-last-merged-rev
>>> V 1
>>> 0
>>> END
>>>
>>> So you mean the "sync-from-url" property? That looks correct, to me (with
>>> my admittedly limited knowledge)
>> Well, I would have used svn pl -r0<repo> to get the list of props (I didn't remember its name) and then svn pg svn:sync-from-url -r0<repo> but I guess it's the same thing.
>>
>> It looks like you're syncing the whole repo. I was just checking :-)
> Okay :)
>
>> Howeve, why is svn:sync-last-merged-rev 0? It should be, well, the last merged revision, 79 I think. I guess svn pg svn:sync-last-merged-rev shows 0 as well?
> Oh, simply because I removed that (destination) repo once it was clear
> it was not correct. I then recreated it this morning in order to perform
> one or other operation you or someone else asked me to do.
>
> If I do it now (having tried to sync again), I get:
> $ cat db/revprops/0/0
> K 8
> svn:date
> V 27
> 2011-03-01T16:14:38.678110Z
> K 26
> svn:sync-currently-copying
> V 2
> 81
> K 17
> svn:sync-from-url
> V 33
> svn://devel.<domain>/<repo>
> K 18
> svn:sync-from-uuid
> V 36
> 7c76b8fe-c8ee-45e6-8ede-b17e10a7e991
> K 24
> svn:sync-last-merged-rev
> V 2
> 80
> END
> as you expected.
>
>>>> Why is it showing files in trunk when you're log command is for
>>>> branches/working ? Or have you just pasted the wrong command?
>>> Nope, that's the command. I mean, it *is* the log, so... shouldn't it?
>>> The commands for trunk and branch produce the same output, anyway:
>>> [12:39:07] jg@ggajg ~/.tmp
>>> $ svn log -v -r80 svn://devel.<domain>/<repo>/trunk> trunk ; svn log -v -r80 svn://devel.<domain>/<repo>/branches/working> branch
>>>
>>> [12:39:26] jg@ggajg ~/.tmp
>>> $ diff -q trunk branch
>>>
>>> [12:39:29] jg@ggajg ~/.tmp
>>>
>> What version of SVN are you using? I've got 1.6.12 and if I am in a directory where no changes were made for a revision then svn log doesn't show anything,>e.g.
>>
>> svn log -v -r17727
>> ------------------------------------------------------------------------
> $ svn --version
> svn, version 1.6.17 (r1128011)
> compiled Jun 2 2011, 10:39:28
>
> I'm not 100% sure what the server version is.
>
>> In the list of files changed in revision 80 that you posted earlier, are there any files at all that are actually in branches/working?
> No, all are in trunk.
That is really baffling me. But mayber that's because you have different
version.
I just thought something else. svnsync stops when trying to create the
branch (rev 81). So maybe the error is something not related to the
repository, like permission (I don't think so though) or some hooks.
Sorry, I am a bit to a dead end here.
Re: svnsync: Error while replaying commit
Posted by Gary <li...@yahoo.co.uk>.
----- Original Message -----
From: Giulio Troccoli
On 02/04/12 11:51, Gary wrote:
> ----- Original Message -----
> From: Giulio Troccoli
> On 02/04/12 11:10, Gary wrote:
>> ----- Original Message -----
>> From: Giulio Troccoli
>>> On 02/04/12 10:24, Gary wrote:
>>>>> that still doesn't explain to me why svnsync barfs on those (not)
>>>>> missing revisions. Looking at the command line history, I can't see
>>>>> anywhere where I pointed svnsync at just the trunk, only ever at the
>>>>> repo/project within the repo (I took my instructions from
>>>>> http://svn.apache.org/repos/asf/subversion/trunk/notes/svnsync.txt)
>>>> Well, at least we know that the revisions are not missing.
>>>>
>>>> Can you show us the source repository path for you synced repo? It
>>>> should be in one of the properties stored in revision 0 in the synced
>>>> repo, if I remember well.
>>> Do you mean in the properties of the one I am trying to sync into, or
>>> from?I'm not really sure what you mean :P
>> Sorry, I wasn't very clear. The one your syncing into, so the
>> destination repo.
>> No problem. I don't know if this is exactly what you want, but:
>> $ cat ./db/revprops/0/0
>> K 8
>> svn:date
>> V 27
>> 2011-03-01T16:14:38.678110Z
>> K 17
>> svn:sync-from-url
>> V 33
>> svn://devel.<domain>/<repo>
>> K 18
>> svn:sync-from-uuid
>> V 36
>> 7c76b8fe-c8ee-45e6-8ede-b17e10a7e991
>> K 24
>> svn:sync-last-merged-rev
>> V 1
>> 0
>> END
>>
>> So you mean the "sync-from-url" property? That looks correct, to me (with
>> my admittedly limited knowledge)
>
>Well, I would have used svn pl -r0 <repo> to get the list of props (I didn't remember its name) and then svn pg svn:sync-from-url -r0 <repo> but I guess it's the same thing.
>
>It looks like you're syncing the whole repo. I was just checking :-)
Okay :)
>Howeve, why is svn:sync-last-merged-rev 0? It should be, well, the last merged revision, 79 I think. I guess svn pg svn:sync-last-merged-rev shows 0 as well?
Oh, simply because I removed that (destination) repo once it was clear
it was not correct. I then recreated it this morning in order to perform
one or other operation you or someone else asked me to do.
If I do it now (having tried to sync again), I get:
$ cat db/revprops/0/0
K 8
svn:date
V 27
2011-03-01T16:14:38.678110Z
K 26
svn:sync-currently-copying
V 2
81
K 17
svn:sync-from-url
V 33
svn://devel.<domain>/<repo>
K 18
svn:sync-from-uuid
V 36
7c76b8fe-c8ee-45e6-8ede-b17e10a7e991
K 24
svn:sync-last-merged-rev
V 2
80
END
as you expected.
>>> Why is it showing files in trunk when you're log command is for
>>> branches/working ? Or have you just pasted the wrong command?
>> Nope, that's the command. I mean, it *is* the log, so... shouldn't it?
>> The commands for trunk and branch produce the same output, anyway:
>> [12:39:07] jg@ggajg ~/.tmp
>> $ svn log -v -r80 svn://devel.<domain>/<repo>/trunk> trunk ; svn log -v -r80 svn://devel.<domain>/<repo>/branches/working> branch
>>
>> [12:39:26] jg@ggajg ~/.tmp
>> $ diff -q trunk branch
>>
>> [12:39:29] jg@ggajg ~/.tmp
>>
>
>What version of SVN are you using? I've got 1.6.12 and if I am in a directory where no changes were made for a revision then svn log doesn't show anything, >e.g.
>
>svn log -v -r17727
>------------------------------------------------------------------------
$ svn --version
svn, version 1.6.17 (r1128011)
compiled Jun 2 2011, 10:39:28
I'm not 100% sure what the server version is.
>In the list of files changed in revision 80 that you posted earlier, are there any files at all that are actually in branches/working?
No, all are in trunk.
Re: svnsync: Error while replaying commit
Posted by Giulio Troccoli <gi...@mediatelgroup.co.uk>.
On 02/04/12 11:51, Gary wrote:
> ----- Original Message -----
> From: Giulio Troccoli
> On 02/04/12 11:10, Gary wrote:
>> ----- Original Message -----
>> From: Giulio Troccoli
>>> On 02/04/12 10:24, Gary wrote:
>>>>> that still doesn't explain to me why svnsync barfs on those (not)
>>>>> missing revisions. Looking at the command line history, I can't see
>>>>> anywhere where I pointed svnsync at just the trunk, only ever at the
>>>>> repo/project within the repo (I took my instructions from
>>>>> http://svn.apache.org/repos/asf/subversion/trunk/notes/svnsync.txt)
>>>> Well, at least we know that the revisions are not missing.
>>>>
>>>> Can you show us the source repository path for you synced repo? It
>>>> should be in one of the properties stored in revision 0 in the synced
>>>> repo, if I remember well.
>>> Do you mean in the properties of the one I am trying to sync into, or
>>> from?I'm not really sure what you mean :P
>> Sorry, I wasn't very clear. The one your syncing into, so the
>> destination repo.
> No problem. I don't know if this is exactly what you want, but:
> $ cat ./db/revprops/0/0
> K 8
> svn:date
> V 27
> 2011-03-01T16:14:38.678110Z
> K 17
> svn:sync-from-url
> V 33
> svn://devel.<domain>/<repo>
> K 18
> svn:sync-from-uuid
> V 36
> 7c76b8fe-c8ee-45e6-8ede-b17e10a7e991
> K 24
> svn:sync-last-merged-rev
> V 1
> 0
> END
>
> So you mean the "sync-from-url" property? That looks correct, to me (with
> my admittedly limited knowledge)
Well, I would have used svn pl -r0 <repo> to get the list of props (I
didn't remember its name) and then svn pg svn:sync-from-url -r0 <repo>
but I guess it's the same thing.
It looks like you're syncing the whole repo. I was just checking :-)
Howeve, why is svn:sync-last-merged-rev 0? It should be, well, the last
merged revision, 79 I think. I guess svn pg svn:sync-last-merged-rev
shows 0 as well?
>>>> Also, can you run svn log -v on revision 80, 81 and 82?
>>> [11:41:02] jg@ggajg ~/.tmp
>>> $ svn log -v -r80 svn://devel.<domain>/<repo>/branches/working
>>> ------------------------------------------------------------------------
>>> r80 | gpspbu | 2011-06-23 16:23:46 +0200 (Thu, 23 Jun 2011) | 1 line
>>> Changed paths:
>>> M /trunk/030-Quellcode/[snip]
>>> A /trunk/030-Quellcode/[snip]
>>> [snip other source code files]
>>>
>>> Added WP31
>>> ------------------------------------------------------------------------
>> Why is it showing files in trunk when you're log command is for
>> branches/working ? Or have you just pasted the wrong command?
> Nope, that's the command. I mean, it *is* the log, so... shouldn't it?
> The commands for trunk and branch produce the same output, anyway:
> [12:39:07] jg@ggajg ~/.tmp
> $ svn log -v -r80 svn://devel.<domain>/<repo>/trunk> trunk ; svn log -v -r80 svn://devel.<domain>/<repo>/branches/working> branch
>
> [12:39:26] jg@ggajg ~/.tmp
> $ diff -q trunk branch
>
> [12:39:29] jg@ggajg ~/.tmp
>
What version of SVN are you using? I've got 1.6.12 and if I am in a
directory where no changes were made for a revision then svn log doesn't
show anything, e.g.
svn log -v -r17727
------------------------------------------------------------------------
In the list of files changed in revision 80 that you posted earlier, are
there any files at all that are actually in branches/working?
Re: svnsync: Error while replaying commit
Posted by Gary <li...@yahoo.co.uk>.
----- Original Message -----
From: Giulio Troccoli
On 02/04/12 11:10, Gary wrote:
> ----- Original Message -----
> From: Giulio Troccoli
>> On 02/04/12 10:24, Gary wrote:
>>>> that still doesn't explain to me why svnsync barfs on those (not)
>>>> missing revisions. Looking at the command line history, I can't see
>>>> anywhere where I pointed svnsync at just the trunk, only ever at the
>>>> repo/project within the repo (I took my instructions from
>>>> http://svn.apache.org/repos/asf/subversion/trunk/notes/svnsync.txt)
>>>
>>> Well, at least we know that the revisions are not missing.
>>>
>>> Can you show us the source repository path for you synced repo? It
>>> should be in one of the properties stored in revision 0 in the synced
>>> repo, if I remember well.
>> Do you mean in the properties of the one I am trying to sync into, or
>> from?I'm not really sure what you mean :P
>
>Sorry, I wasn't very clear. The one your syncing into, so the
>destination repo.
No problem. I don't know if this is exactly what you want, but:
$ cat ./db/revprops/0/0
K 8
svn:date
V 27
2011-03-01T16:14:38.678110Z
K 17
svn:sync-from-url
V 33
svn://devel.<domain>/<repo>
K 18
svn:sync-from-uuid
V 36
7c76b8fe-c8ee-45e6-8ede-b17e10a7e991
K 24
svn:sync-last-merged-rev
V 1
0
END
So you mean the "sync-from-url" property? That looks correct, to me (with
my admittedly limited knowledge)
>>> Also, can you run svn log -v on revision 80, 81 and 82?
>> [11:41:02] jg@ggajg ~/.tmp
>> $ svn log -v -r80 svn://devel.<domain>/<repo>/branches/working
>> ------------------------------------------------------------------------
>> r80 | gpspbu | 2011-06-23 16:23:46 +0200 (Thu, 23 Jun 2011) | 1 line
>> Changed paths:
>> M /trunk/030-Quellcode/[snip]
>> A /trunk/030-Quellcode/[snip]
>> [snip other source code files]
>>
>> Added WP31
>> ------------------------------------------------------------------------
>
>Why is it showing files in trunk when you're log command is for
>branches/working ? Or have you just pasted the wrong command?
Nope, that's the command. I mean, it *is* the log, so... shouldn't it?
The commands for trunk and branch produce the same output, anyway:
[12:39:07] jg@ggajg ~/.tmp
$ svn log -v -r80 svn://devel.<domain>/<repo>/trunk > trunk ; svn log -v -r80 svn://devel.<domain>/<repo>/branches/working > branch
[12:39:26] jg@ggajg ~/.tmp
$ diff -q trunk branch
[12:39:29] jg@ggajg ~/.tmp
> ------------------------------------------------------------------------
Re: svnsync: Error while replaying commit
Posted by Giulio Troccoli <gi...@mediatelgroup.co.uk>.
On 02/04/12 11:10, Gary wrote:
> ----- Original Message -----
> From: Giulio Troccoli
>> On 02/04/12 10:24, Gary wrote:
>>> This is perhaps better:
>>>
>>> $ svn log svn://devel.<domain>/<repo>/
>>> [snip]
>>> ------------------------------------------------------------------------
>>> r84 | gpspbu | 2011-06-24 12:52:16 +0200 (Fri, 24 Jun 2011) | 1 line
>>>
>>> merged trunk to branch
>>> ------------------------------------------------------------------------
>>> r83 | gpspbu | 2011-06-24 12:34:38 +0200 (Fri, 24 Jun 2011) | 1 line
>>>
>>> added missing file
>>> ------------------------------------------------------------------------
>>> r82 | ggapbu | 2011-06-23 17:58:49 +0200 (Thu, 23 Jun 2011) | 1 line
>>>
>>> test
>>> ------------------------------------------------------------------------
>>> r81 | gpspbu | 2011-06-23 17:48:03 +0200 (Thu, 23 Jun 2011) | 1 line
>>>
>>> Created a branch working of /<repo>/trunk.
>>> ------------------------------------------------------------------------
>>> r80 | gpspbu | 2011-06-23 16:23:46 +0200 (Thu, 23 Jun 2011) | 1 line
>>>
>>> Added WP31
>>> ------------------------------------------------------------------------
>>> [snip]
>>>
>>> But that still doesn't explain to me why svnsync barfs on those (not)
>>> missing revisions. Looking at the command line history, I can't see
>>>
>>> anywhere where I pointed svnsync at just the trunk, only ever at the
>>>
>>> repo/project within the repo (I took my instructions from
>>> http://svn.apache.org/repos/asf/subversion/trunk/notes/svnsync.txt)
>>>
>> Well, at least we know that the revisions are not missing.
>>
>> Can you show us the source repository path for you synced repo? It
>> should be in one of the properties stored in revision 0 in the synced
>> repo, if I remember well.
> Do you mean in the properties of the one I am trying to sync into, or
> from?I'm not really sure what you mean :P
Sorry, I wasn't very clear. The one your syncing into, so the
destination repo.
>> Also, can you run svn log -v on revision 80, 81 and 82?
> [11:41:02] jg@ggajg ~/.tmp
> $ svn log -v -r80 svn://devel.<domain>/<repo>/branches/working
> ------------------------------------------------------------------------
> r80 | gpspbu | 2011-06-23 16:23:46 +0200 (Thu, 23 Jun 2011) | 1 line
> Changed paths:
> M /trunk/030-Quellcode/[snip]
> A /trunk/030-Quellcode/[snip]
> [snip other source code files]
>
> Added WP31
> ------------------------------------------------------------------------
Why is it showing files in trunk when you're log command is for
branches/working ? Or have you just pasted the wrong command?
> [11:41:08] jg@ggajg ~/.tmp
> $ svn log -v -r81 svn://devel.<domain>/<repo>/branches/working
> ------------------------------------------------------------------------
> r81 | gpspbu | 2011-06-23 17:48:03 +0200 (Thu, 23 Jun 2011) | 1 line
> Changed paths:
> A /branches/working (from /trunk:80)
>
> Created a branch working of /<repo>/trunk.
> ------------------------------------------------------------------------
>
> [11:41:21] jg@ggajg ~/.tmp
> $ svn log -v -r82 svn://devel.<domain>/<repo>/branches/working
> ------------------------------------------------------------------------
> r82 | ggapbu | 2011-06-23 17:58:49 +0200 (Thu, 23 Jun 2011) | 1 line
> Changed paths:
> A /branches/working/030-Quellcode/GPSAssemblies/test.txt
>
> test
> ------------------------------------------------------------------------
Re: svnsync: Error while replaying commit
Posted by Gary <li...@yahoo.co.uk>.
----- Original Message -----
From: Giulio Troccoli
> On 02/04/12 10:24, Gary wrote:
>> This is perhaps better:
>>
>> $ svn log svn://devel.<domain>/<repo>/
>> [snip]
>> ------------------------------------------------------------------------
>> r84 | gpspbu | 2011-06-24 12:52:16 +0200 (Fri, 24 Jun 2011) | 1 line
>>
>> merged trunk to branch
>> ------------------------------------------------------------------------
>> r83 | gpspbu | 2011-06-24 12:34:38 +0200 (Fri, 24 Jun 2011) | 1 line
>>
>> added missing file
>> ------------------------------------------------------------------------
>> r82 | ggapbu | 2011-06-23 17:58:49 +0200 (Thu, 23 Jun 2011) | 1 line
>>
>> test
>> ------------------------------------------------------------------------
>> r81 | gpspbu | 2011-06-23 17:48:03 +0200 (Thu, 23 Jun 2011) | 1 line
>>
>> Created a branch working of /<repo>/trunk.
>> ------------------------------------------------------------------------
>> r80 | gpspbu | 2011-06-23 16:23:46 +0200 (Thu, 23 Jun 2011) | 1 line
>>
>> Added WP31
>> ------------------------------------------------------------------------
>> [snip]
>>
>> But that still doesn't explain to me why svnsync barfs on those (not)
>> missing revisions. Looking at the command line history, I can't see
>>
>> anywhere where I pointed svnsync at just the trunk, only ever at the
>>
>> repo/project within the repo (I took my instructions from
>> http://svn.apache.org/repos/asf/subversion/trunk/notes/svnsync.txt)
>>
>
>Well, at least we know that the revisions are not missing.
>
>Can you show us the source repository path for you synced repo? It
>should be in one of the properties stored in revision 0 in the synced
>repo, if I remember well.
Do you mean in the properties of the one I am trying to sync into, or
from?I'm not really sure what you mean :P
>Also, can you run svn log -v on revision 80, 81 and 82?
[11:41:02] jg@ggajg ~/.tmp
$ svn log -v -r80 svn://devel.<domain>/<repo>/branches/working
------------------------------------------------------------------------
r80 | gpspbu | 2011-06-23 16:23:46 +0200 (Thu, 23 Jun 2011) | 1 line
Changed paths:
M /trunk/030-Quellcode/[snip]
A /trunk/030-Quellcode/[snip]
[snip other source code files]
Added WP31
------------------------------------------------------------------------
[11:41:08] jg@ggajg ~/.tmp
$ svn log -v -r81 svn://devel.<domain>/<repo>/branches/working
------------------------------------------------------------------------
r81 | gpspbu | 2011-06-23 17:48:03 +0200 (Thu, 23 Jun 2011) | 1 line
Changed paths:
A /branches/working (from /trunk:80)
Created a branch working of /<repo>/trunk.
------------------------------------------------------------------------
[11:41:21] jg@ggajg ~/.tmp
$ svn log -v -r82 svn://devel.<domain>/<repo>/branches/working
------------------------------------------------------------------------
r82 | ggapbu | 2011-06-23 17:58:49 +0200 (Thu, 23 Jun 2011) | 1 line
Changed paths:
A /branches/working/030-Quellcode/GPSAssemblies/test.txt
test
------------------------------------------------------------------------
Re: svnsync: Error while replaying commit
Posted by Giulio Troccoli <gi...@mediatelgroup.co.uk>.
On 02/04/12 10:24, Gary wrote:
> From: Giulio Troccoli
> On 02/04/12 08:27, Gary wrote:
>>> ----- Original Message -----
>>> From: Henrik Sundberg
>>>
>>>> Do you have a precommit hook now that was not there when revs 81-82
>>> were committed?
>>> There are no hooks as far as I know. (I'm not an admin, and the admin is not very forthcoming on.. well, anything, really).
>>>
>>>
>>>> Svn log will show the revisions whereever in the repository they were
>>>> made. Are they missing for real?
>>> Yes the revisions are really missing:
>>> $ svn log
>> Did you run svn log on the working copy? I ask because it's really
>> strange that two revisions are missing so maybe they have been made on a
>> different part of the repository. I would suggest running svn info to
>> get the correct repository URL and then run svn log against that URL.
> Hmm. Yeah, I ran it on a working copy, just based on what Henrik said.
> I wasn't really thinking (being on call will do that to a chap)... Sorry.
> This is perhaps better:
>
> $ svn log svn://devel.<domain>/<repo>/
> [snip]
> ------------------------------------------------------------------------
> r84 | gpspbu | 2011-06-24 12:52:16 +0200 (Fri, 24 Jun 2011) | 1 line
>
> merged trunk to branch
> ------------------------------------------------------------------------
> r83 | gpspbu | 2011-06-24 12:34:38 +0200 (Fri, 24 Jun 2011) | 1 line
>
> added missing file
> ------------------------------------------------------------------------
> r82 | ggapbu | 2011-06-23 17:58:49 +0200 (Thu, 23 Jun 2011) | 1 line
>
> test
> ------------------------------------------------------------------------
> r81 | gpspbu | 2011-06-23 17:48:03 +0200 (Thu, 23 Jun 2011) | 1 line
>
> Created a branch working of /<repo>/trunk.
> ------------------------------------------------------------------------
> r80 | gpspbu | 2011-06-23 16:23:46 +0200 (Thu, 23 Jun 2011) | 1 line
>
> Added WP31
> ------------------------------------------------------------------------
> [snip]
>
> But that still doesn't explain to me why svnsync barfs on those (not)
> missing revisions. Looking at the command line history, I can't see
>
> anywhere where I pointed svnsync at just the trunk, only ever at the
>
> repo/project within the repo (I took my instructions from
> http://svn.apache.org/repos/asf/subversion/trunk/notes/svnsync.txt)
>
Well, at least we know that the revisions are not missing.
Can you show us the source repository path for you synced repo? It
should be in one of the properties stored in revision 0 in the synced
repo, if I remember well.
Also, can you run svn log -v on revision 80, 81 and 82?
>
>> On Fri, Mar 30, 2012 at 15:25, Gary<li...@yahoo.co.uk> wrote:
>>> I see a lot of reports of this error, but little in the way of
>>> clear information as to what it might mean, or how to fix it:
>>>
>>> $ svnsync sync file://`pwd`/dest
>>> Committed revision 1.
>>> Copied properties for revision 1.
>>> Transmitting file data .....................
>>> [...]
>>> Committed revision 79.
>>> Copied properties for revision 79.
>>> Transmitting file data .......................
>>> Committed revision 80.
>>> Copied properties for revision 80.
>>> svnsync: Error while replaying commit
>>>
>>> Huh?
>>>
>>> If I look at the source server log, revs 81& 82 are "missing"
>>> in the trunk. I imagine they are/were in a branch, which AFAIK
>>> is no longer available. Is there any way to get around this?
>>> Assuming that's the problem, of course.
>>>
> ----- Original Message -----
>
Re: svnsync: Error while replaying commit
Posted by Gary <li...@yahoo.co.uk>.
From: Giulio Troccoli
On 02/04/12 08:27, Gary wrote:
>> ----- Original Message -----
>> From: Henrik Sundberg
>>
>>> Do you have a precommit hook now that was not there when revs 81-82
>> were committed?
>> There are no hooks as far as I know. (I'm not an admin, and the admin is not very forthcoming on.. well, anything, really).
>>
>>
>>> Svn log will show the revisions whereever in the repository they were
>>> made. Are they missing for real?
>> Yes the revisions are really missing:
>> $ svn log
>
>Did you run svn log on the working copy? I ask because it's really
>strange that two revisions are missing so maybe they have been made on a
>different part of the repository. I would suggest running svn info to
>get the correct repository URL and then run svn log against that URL.
Hmm. Yeah, I ran it on a working copy, just based on what Henrik said.
I wasn't really thinking (being on call will do that to a chap)... Sorry.
This is perhaps better:
$ svn log svn://devel.<domain>/<repo>/
[snip]
------------------------------------------------------------------------
r84 | gpspbu | 2011-06-24 12:52:16 +0200 (Fri, 24 Jun 2011) | 1 line
merged trunk to branch
------------------------------------------------------------------------
r83 | gpspbu | 2011-06-24 12:34:38 +0200 (Fri, 24 Jun 2011) | 1 line
added missing file
------------------------------------------------------------------------
r82 | ggapbu | 2011-06-23 17:58:49 +0200 (Thu, 23 Jun 2011) | 1 line
test
------------------------------------------------------------------------
r81 | gpspbu | 2011-06-23 17:48:03 +0200 (Thu, 23 Jun 2011) | 1 line
Created a branch working of /<repo>/trunk.
------------------------------------------------------------------------
r80 | gpspbu | 2011-06-23 16:23:46 +0200 (Thu, 23 Jun 2011) | 1 line
Added WP31
------------------------------------------------------------------------
[snip]
But that still doesn't explain to me why svnsync barfs on those (not)
missing revisions. Looking at the command line history, I can't see
anywhere where I pointed svnsync at just the trunk, only ever at the
repo/project within the repo (I took my instructions from
http://svn.apache.org/repos/asf/subversion/trunk/notes/svnsync.txt)
> On Fri, Mar 30, 2012 at 15:25, Gary<li...@yahoo.co.uk> wrote:
>> I see a lot of reports of this error, but little in the way of
>> clear information as to what it might mean, or how to fix it:
>>
>> $ svnsync sync file://`pwd`/dest
>> Committed revision 1.
>> Copied properties for revision 1.
>> Transmitting file data .....................
>> [...]
>> Committed revision 79.
>> Copied properties for revision 79.
>> Transmitting file data .......................
>> Committed revision 80.
>> Copied properties for revision 80.
>> svnsync: Error while replaying commit
>>
>> Huh?
>>
>> If I look at the source server log, revs 81& 82 are "missing"
>> in the trunk. I imagine they are/were in a branch, which AFAIK
>> is no longer available. Is there any way to get around this?
>> Assuming that's the problem, of course.
>>
----- Original Message -----
Re: svnsync: Error while replaying commit
Posted by Giulio Troccoli <gi...@mediatelgroup.co.uk>.
On 02/04/12 08:27, Gary wrote:
> ----- Original Message -----
> From: Henrik Sundberg
>
>> Do you have a precommit hook now that was not there when revs 81-82
> were committed?
> There are no hooks as far as I know. (I'm not an admin, and the admin is not very forthcoming on.. well, anything, really).
>
>
>> Svn log will show the revisions whereever in the repository they were
>> made. Are they missing for real?
> Yes the revisions are really missing:
> $ svn log
Did you run svn log on the working copy? I ask because it's really
strange that two revisions are missing so maybe they have been made on a
different part of the repository. I would suggest running svn info to
get the correct repository URL and then run svn log against that URL.
> [snip]
> ------------------------------------------------------------------------
> r83 | gpspbu | 2011-06-24 12:34:38
> +0200 (Fri, 24 Jun 2011) | 1 line
>
> added missing file
> ------------------------------------------------------------------------
> r80 | gpspbu | 2011-06-23 16:23:46
> +0200 (Thu, 23 Jun 2011) | 1 line
>
> Added WP31
> ------------------------------------------------------------------------
> r79 | gpspbu | 2011-06-23 15:58:15
> +0200 (Thu, 23 Jun 2011) | 1 line
>
> Added a PhoneNumberUnlocker
> ------------------------------------------------------------------------
>
>
>
> On Fri, Mar 30, 2012 at 15:25, Gary<li...@yahoo.co.uk> wrote:
>> I see a lot of reports of this error, but little in the way of
>> clear information as to what it might mean, or how to fix it:
>>
>> $ svnsync sync file://`pwd`/dest
>> Committed revision 1.
>> Copied properties for revision 1.
>> Transmitting file data .....................
>> [...]
>> Committed revision 79.
>> Copied properties for revision 79.
>> Transmitting file data .......................
>> Committed revision 80.
>> Copied properties for revision 80.
>> svnsync: Error while replaying commit
>>
>> Huh?
>>
>> If I look at the source server log, revs 81& 82 are "missing"
>> in the trunk. I imagine they are/were in a branch, which AFAIK
>> is no longer available. Is there any way to get around this?
>> Assuming that's the problem, of course.
>>
Re: svnsync: Error while replaying commit
Posted by Gary <li...@yahoo.co.uk>.
----- Original Message -----
From: Henrik Sundberg
> Do you have a precommit hook now that was not there when revs 81-82
were committed?
There are no hooks as far as I know. (I'm not an admin, and the admin is not very forthcoming on.. well, anything, really).
> Svn log will show the revisions whereever in the repository they were
> made. Are they missing for real?
Yes the revisions are really missing:
$ svn log
[snip]
------------------------------------------------------------------------
r83 | gpspbu | 2011-06-24 12:34:38
+0200 (Fri, 24 Jun 2011) | 1 line
added missing file
------------------------------------------------------------------------
r80 | gpspbu | 2011-06-23 16:23:46
+0200 (Thu, 23 Jun 2011) | 1 line
Added WP31
------------------------------------------------------------------------
r79 | gpspbu | 2011-06-23 15:58:15
+0200 (Thu, 23 Jun 2011) | 1 line
Added a PhoneNumberUnlocker
------------------------------------------------------------------------
On Fri, Mar 30, 2012 at 15:25, Gary <li...@yahoo.co.uk> wrote:
> I see a lot of reports of this error, but little in the way of
> clear information as to what it might mean, or how to fix it:
>
> $ svnsync sync file://`pwd`/dest
> Committed revision 1.
> Copied properties for revision 1.
> Transmitting file data .....................
> [...]
> Committed revision 79.
> Copied properties for revision 79.
> Transmitting file data .......................
> Committed revision 80.
> Copied properties for revision 80.
> svnsync: Error while replaying commit
>
> Huh?
>
> If I look at the source server log, revs 81 & 82 are "missing"
> in the trunk. I imagine they are/were in a branch, which AFAIK
> is no longer available. Is there any way to get around this?
> Assuming that's the problem, of course.
>
Re: svnsync: Error while replaying commit
Posted by Henrik Sundberg <st...@gmail.com>.
Do you have a precommit hook now that was not there when revs 81-82
were committed?
Svn log will show the revisions whereever in the repository they were
made. Are they missing for real?
/$
On Fri, Mar 30, 2012 at 15:25, Gary <li...@yahoo.co.uk> wrote:
> I see a lot of reports of this error, but little in the way of
> clear information as to what it might mean, or how to fix it:
>
> $ svnsync sync file://`pwd`/dest
> Committed revision 1.
> Copied properties for revision 1.
> Transmitting file data .....................
> [...]
> Committed revision 79.
> Copied properties for revision 79.
> Transmitting file data .......................
> Committed revision 80.
> Copied properties for revision 80.
> svnsync: Error while replaying commit
>
> Huh?
>
> If I look at the source server log, revs 81 & 82 are "missing"
> in the trunk. I imagine they are/were in a branch, which AFAIK
> is no longer available. Is there any way to get around this?
> Assuming that's the problem, of course.
>
Re: svnsync: Error while replaying commit
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Haven't read the whole thread, but the problem here has to do with r81.
r80 moved fine and I expect `svnlook youngest dest` = 80.
If the source repos has authz set up or has undergone history surgeries
that's likely related.
You could try running:
% svnserve --log-file=foo.log -dr.
% svnsync sync svn://localhost
to get a "destination server" log.
Gary wrote on Fri, Mar 30, 2012 at 14:25:28 +0100:
> I see a lot of reports of this error, but little in the way of
> clear information as to what it might mean, or how to fix it:
>
> $ svnsync sync file://`pwd`/dest
> Committed revision 1.
> Copied properties for revision 1.
> Transmitting file data .....................
> [...]
> Committed revision 79.
> Copied properties for revision 79.
> Transmitting file data .......................
> Committed revision 80.
> Copied properties for revision 80.
> svnsync: Error while replaying commit
>
> Huh?
>
> If I look at the source server log, revs 81 & 82 are "missing"
> in the trunk. I imagine they are/were in a branch, which AFAIK
> is no longer available. Is there any way to get around this?
> Assuming that's the problem, of course.
>