-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No such file or directory; failed to install file 'themes\'. #681
Comments
Aw man. I tried to test all the things thoroughly. I must have missed something specifically about the zip update mechanism. I'll look into it tonight. You can try installing with the setup.exe program and that should work. |
Sigh. The updater has a bug that doesn't support subdirectories under the Clink program directory. And Clink v1.7.0 now includes a The updater updated everything except the new For now, you can go to the latest release and manually extract the I'll work on solving the updater issue. |
Yes. In testing, it worked. But in the live update it's still hitting a specific problem that I already fixed during the testing. I'm investigating, and deleting v1.7.1. |
It's working fine with test builds. But not with release builds. It deletes the files in a directory, and deletes the directory. It almost seems like it might be a timing issue with antivirus software. |
I've added logging and retries. This is very frustrating for me, because I'm doing detailed and time consuming tests. Here comes attempt number 3... 😕 |
Still the same error (Windows 11, admin user):
|
I can also confirm the same error under Windows 10:
|
v1.7.2 solves the problem. But you have to update twice: run I think maybe v1.7.1 had already solved the problem: The first update fails; there's no way around that. Because when updating from version X to version Y, the updater code that's running is from version X. I forgot to explain that two updates are necessary to finish the update. |
@d4k0 You have to start a new Clink session after the initial error, and then it will finish the update. There's nothing I can do to prevent the initial error -- the code for that is already on everyone's machines. |
Ah, the second run of |
The initial update reports an error. Start a new Clink session after the error, and it will finish the update successfully.There's nothing that can be done to prevent the initial error because it's running the updater code that's already on your computer from the older copy of Clink. I can't even add a clarifying message. Because the updater code is always from the previous version of Clink -- it's never from the new version. 😓 |
thanks, second update worked:
|
Confirmed, runnig the update a 2nd time works. 👍 |
For some reason on my machine, although the update completed the second time successfully, I still cannot use any of the new color themes or prompts. I have stock settings so it can't be any lua script interfering. |
For tracking purposes I've moved that to a new separate issue #682, since it's not related to this issue. |
Closing this now, as the issue is fixed and mitigated, and running |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
Moved three comments to #692 for tracking purposes because they're a separate issue (hid the comments here as "duplicate"). |
I made the update to from 1.6.21 to 1.7.0 and saw the message during update:
Update worked, I'm now at 1.7.0, but I'm a bit confused by this message.
The text was updated successfully, but these errors were encountered: