Pristine install stream error - easy to reproduce

[Krzysztof Rosół]

Hello,

I am using Windows 10 and have encountered an issue with TortoiseSVN related to the TEMP folder location.

From experience, I know that the TEMP and AppData folders in Windows fill up quickly. To avoid disk space issues on drive C, I created a separate drive T, moved the TEMP folders there, and updated the paths in the system environment variables. This setup works fine for all other applications, but I am experiencing issues with TortoiseSVN.

The problem most commonly occurs when attempting to commit after restarting the computer. Each time, I need to run a cleanup before I can proceed. I even tried disabling Windows' automatic cleanup features (I don’t use CCleaner or similar software), but the issue persists.

I also use TortoiseSVN on other machines, including a virtual machine, and everything works fine as long as the TEMP folder remains on drive C. However, when TEMP is on another drive, I frequently encounter errors like "Pristine install steam."

Would it be possible to develop a patch to resolve this issue? It seems that TortoiseSVN does not handle TEMP directories outside of drive C properly (even on the same SSD drive), while other applications work without issues. Let me know if this is something that could be addressed in a future update.

[Daniel Sahlberg]

fredag 21 februari 2025 kl. 12:03:28 UTC+1 skrev krzyszt...@gmail.com:

Hello,

I am using Windows 10 and have encountered an issue with TortoiseSVN related to the TEMP folder location.

From experience, I know that the TEMP and AppData folders in Windows fill up quickly. To avoid disk space issues on drive C, I created a separate drive T, moved the TEMP folders there, and updated the paths in the system environment variables. This setup works fine for all other applications, but I am experiencing issues with TortoiseSVN.

Is %TEMP% pointing directly to T: or to a subfolder?

 

The problem most commonly occurs when attempting to commit after restarting the computer. Each time, I need to run a cleanup before I can proceed. I even tried disabling Windows' automatic cleanup features (I don’t use CCleaner or similar software), but the issue persists.

With "cleanup", I assume you mean the "Clean up..." option on the TortoiseSVN context menu. This is required since Subversion crashed in the middle of an operation, it restores the working copy internal database.

Do you make any other changes than just "Clean up..." - for example permissions?

Do you have the working copy in the TEMP folder or some place else (on C: or on T:)?

 

I also use TortoiseSVN on other machines, including a virtual machine, and everything works fine as long as the TEMP folder remains on drive C. However, when TEMP is on another drive, I frequently encounter errors like "Pristine install steam."

Would it be possible to develop a patch to resolve this issue? It seems that TortoiseSVN does not handle TEMP directories outside of drive C properly (even on the same SSD drive), while other applications work without issues. Let me know if this is something that could be addressed in a future update.

Can you install the command line tools and retry the same operation? Basically just

C:\>svn commit "c:\path\to\working\copy" -m "some commit message"

If you get the same error using the command line, please send this to us...@subversion.apache.org instead, since the error originates in the Subversion library.

Cheers,

Daniel