svn copy WC to URL asserts

109 views
Skip to first unread message

Jens Geyer

unread,
Aug 15, 2018, 10:16:58 AM8/15/18
to us...@subversion.apache.org

Hi,

 

We have one case of a misbehaving branch here. Our CI server creates a tag at the end of a build using a svn copy command:


{code}

svn.exe copy -m "Devtest" D:\Builds\Release_5.1.1.x\Source svn://repo.server/tags/buildserver/Release_5.1.1.x/Build513

{code}

 

The message printed is this.


{code}

svn: E235000: In file 'D:\Development\SVN\Releases\TortoiseSVN-1.10.1ext\subversion\subversion\libsvn_client\copy.c' line 2109: assertion failed (commit_items != NULL)

{code}

 


The problem so far manifests only with this particular branch. We double-checked everything, beginning with paths and URLs up to access permisions and everything. We also installed the latest SVN version, and as the only result the assertion line number changed.

The WC has no changes, but a bunch of externals.

 

 

Any advice where to look for or what to check would be appreciated. If I can provide information to help fixing the issue, please let me know and I will be happy to supply whatever informatiomn you may need (except that I am certainly not going to upload the repo nor the complete source code).

 

 

Best regards,

Jens Geyer

 

Branko Čibej

unread,
Oct 27, 2018, 12:07:17 PM10/27/18
to us...@subversion.apache.org, Jens Geyer
[Note, this is issue #4769, which the OP already created. In future, please read the big yellow box at https://subversion.apache.org/reporting-issues.html ]

Can you please do the following:

svn.exe info --show-item=repos-root-url D:\Builds\Release_5.1.1.x\Source

then check if the printed URL matches the target URL of the copy? That assertion implies that you're trying to copy to a different repository than the working copy was checked out from.

-- Brane



Branko Čibej

unread,
Oct 27, 2018, 12:11:18 PM10/27/18
to us...@subversion.apache.org, Jens Geyer
Or of course you could try:

svn.exe copy --ignore-externals ...

since copying the externals contents may well be the cause of the problem if the externals point to different repositories. Since you're creating a "tag" you may want to use the --pin-externals flag, too, unless your externals references are already pinned.

-- Brane
Reply all
Reply to author
Forward
0 new messages