TortoiseSVN 1.14.5 svn: E235000 assertion failed (commit_items != NULL)

[Jesse k]

Hello,

On my new system using windows 11 I get the following error when trying to create a tag via the command line: "svn: E235000: In file 'D:\Development\SVN\Releases\TortoiseSVN-1.14.5\ext\subversion\subversion\libsvn_client\copy.c' line 2100: assertion failed (commit_items != NULL)"

Using the following command: "svn copy -m "insert message" "insert path to file" "insert server URL""

The same copy command does work on my previous system using windows 10. And it also seems to be exclusive if the repo is on the server. I have tested this by creating a temporary local repo were I was able to make a copy/tag of a file succesfully.

Also the tag can be succesfully created if I manually create it using the tag/branch window.

Is this a (windows 11) bug? or might it be related to something else?

Used software information on both systems:

TortoiseSVN 1.14.5, Build 29465 - 64 Bit , 2022/09/24 08:31:31

ipv6 enabled
Subversion 1.14.2, -release
apr 1.6.5
apr-util 1.6.1
serf 1.3.9
OpenSSL 1.1.1n  15 Mar 2022
zlib 1.2.11
SQLite 3.36.0

[Daniel Sahlberg]

onsdag 17 januari 2024 kl. 13:55:32 UTC+1 skrev Jesse k:

Hello,

On my new system using windows 11 I get the following error when trying to create a tag via the command line: "svn: E235000: In file 'D:\Development\SVN\Releases\TortoiseSVN-1.14.5\ext\subversion\subversion\libsvn_client\copy.c' line 2100: assertion failed (commit_items != NULL)"

Using the following command: "svn copy -m "insert message" "insert path to file" "insert server URL""

The same copy command does work on my previous system using windows 10. And it also seems to be exclusive if the repo is on the server. I have tested this by creating a temporary local repo were I was able to make a copy/tag of a file succesfully.

Since this is reproducible using the Subversion command line client you are probably better of by asking at the Subversion users@ mailing list, see https://subversion.apache.org/mailing-lists.html. If you post the same report there someone will probably be able to take a look.

Still, I'd like to ask a few questions which may help in debugging:

- Can you try it with the latest version (TortoiseSVN 1.14.6, using Subversion 1.14.3)? I checked the code quickly and I don't think it has changed but it always helps to test with the latest version.

- Do you have any local modifications?

- Is the Server URL and the repository URL (see svn info) in the same repository? Can you share the URLs (you can replace the server name with "svn.example.com" if you don't want to expose this).

 

Kind regards,

Daniel

[Jesse k]

Hello Daniel,

Thank you for your quick help and guidance. In the mean time I have figured out what the cause of the issue is and I have been comparing the URLs in our batch files and the ones used in the tag/branch window. Here I noticed that the repository name was written with a capital letter in our batch files. While the repository name is written without a capital letter... After changing this everything worked as it did before. 

I have not yet wrapped my head around as to why this suddenly is an issue and why this only occures on my new system as I have described. None of my colleagues had this issue either and the URL in the batch files have been the same for years..

Kind regards,

Jesse

Op woensdag 17 januari 2024 om 14:06:28 UTC+1 schreef Daniel Sahlberg: