While testing the final Dangerzone 0.6.0 MSI on Windows, I stumbled on the following error:
The message reads:
[WinError 32] The process cannot access the file because it is being used by another process: [path to temporary file]
I tested the Dangerzone 0.5.1 MSI, and the same error occurs, so this is not a release blocker. Still, it seems that we don't test for this scenario in our QA, and that's why it's slipped all this time. We should:
Figure out which process keeps this file open, and
While testing the final Dangerzone 0.6.0 MSI on Windows, I stumbled on the following error:
The message reads:
I tested the Dangerzone 0.5.1 MSI, and the same error occurs, so this is not a release blocker. Still, it seems that we don't test for this scenario in our QA, and that's why it's slipped all this time. We should: