torsdag 26 januari 2023 kl. 08:48:27 UTC+1 skrev [email protected]: Hi, We are having a problem with TortoiseSVN 1.14.5, Build 29465 - 64 Bit and earlier versions. When we want to clone, update or commit with a working copy that is placed under a WSL2 folder, TortoiseSVN does not work. The issue is already reported by others on WSL issue tracker: https://github.com/microsoft/WSL/issues/4689.
I understand the issue is caused by SVN itself (actually the sqlLite database used internally) but I was wodnering if somebody has some workaround for this? Are more people suffering from this problem? We think TortoiseSVN is great and we also believe WSL is great. It would be awesome to be able to combine those. I think you analysis is correct and I can't find any way to disable the SQLite locking. There is also a separate issue in the sqlitebrowser project: https://github.com/sqlitebrowser/sqlitebrowser/issues/2142 Can you work around the issue by placing the working copy within Windows and accessing it through /mnt/driveletter/path from WSL? Please be aware that TortoiseSVN is using Windows-style line endings (CRLF) whereas most Unix tools (including Subversion under WSL) expect/require Unix-style line endings (plain LF). Subversion has support to translate source files on commit/update, see the svn:eol-style property. If this is used and Subversion encounter a file with unexpected line endings (for example if you use the svn command line client in WSL on a working copy created by TortoiseSVN) you will run into problems. Kind regards, Daniel -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/ae5c9792-1eeb-4fe1-aca5-15df76261043n%40googlegroups.com.
