"The parameter is incorrect." on "SVN check for Modifications"

168 views
Skip to first unread message

Martin Jost

unread,
Nov 25, 2020, 6:57:23 AM11/25/20
to TortoiseSVN
What I did:
I'm using "TortoiseSVN 1.14.0, Build 28885 - 64 Bit , 2020/05/24 13:32:45", the newest version in my understanding.
I mostly work under Linux, but really like some TortoiseSVN features.
So I use it via SMB on my home directory on Windows (Win 10)
There I ran "SVN check for Modifications" on my workspace.

What I expected
The list of my modified files, so I can commit.

What happened:
The window came up, just with
"Can't read file
'<Repo-path\Symlink-file>':
The parameter is incorrect."

Notes:
The file it complains about, is one of my symlinks. I guess, this is the problem and the "incorrect parameter".
In the past, this worked in Tortoise SVN, I "just" had to be ultra-careful about the symlinks.
(I had these in a Changeset of its own)
Unfortunately, I can't tell when/why it broke now.

My favorite solution would be to get the functionality back.
If this is not possible, a better error message would be nice.
(I know, I'm stretching Tortoise SVN here...)

Stefan

unread,
Nov 25, 2020, 12:05:58 PM11/25/20
to TortoiseSVN
as newer svn (and the underlying apr lib) versions have improvements with dealing with symlinks and junctions on Windows, the problem here might be that your SMB reports the symlink as a Windows symlink, but then does not provide the proper response when svn then tries to resolve that symlink with the corresponding windows APIs.

why not just do a checkout on Windows so you get another working copy?


Martin Jost

unread,
Nov 26, 2020, 5:42:51 AM11/26/20
to TortoiseSVN
Hello,
"why not just do a checkout on Windows so you get another working copy?"
Because the test is done on Unix. If I check out on Windows to a Windows-drive, I have no chance to test.
(Doing hard realtime SW, which needs to run on the specific target, our CI also runs on Unix; the part I had a fight with, is an update to the scripting for CI)

Regards
Martin
Reply all
Reply to author
Forward
0 new messages