[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn copy WC to URL asserts

From: Branko Čibej <brane_at_apache.org>
Date: Sat, 27 Oct 2018 18:07:12 +0200

On 15.08.2018 16:14, Jens Geyer wrote:
>
> 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).
>

[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
Received on 2018-10-27 18:07:23 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.