T: 0044 (0) 20 7553 80285 | M: 0044 (0) 7887 736749 | E: pe.yo...@sap.com
http://www.sap.com
svn-mh-vm:/export/svn${SVNBIN}svnsync sync --username pyoung --password
pyoung
file:///export/svn/aleri
svnsync: Error while replaying commit
hmomh:/export/svnsvn log file:///export/svn/aleri| grep r282
Subject:svnsync: Error while replaying commit
:svnsync: Error while replaying commit
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.
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
.
[...]
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
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
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
From: Ulrich Eckhardt ulrich.eckha...@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
deleteing a branch
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
- 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
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
- 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
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
- 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
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
- 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
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
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
.
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
Hi,
I've had a svnsync job running every day since Mar 3 with no issues. Today May
5 it will no longer synchronize with the below error. Any way to fix this
without starting over (if that would work)?
svnsync synchronize file:///misc_sourcectrl01/svnrepositories/GRCC
svnsync: Error while
21 matches
Mail list logo
