-
Notifications
You must be signed in to change notification settings - Fork 74
Patch failed to apply at second update on Windows #47
Comments
During second update on Windows, log says following error: Traceback (most recent call last): |
Further investigation prevails Esky do not seek root privilege on second update the way it happens on first time update when self.version_finder.has_version() throws exception making Esky.auto_update() to beg for get_root() and re-do everything again. Hope this will help quick-fix this issue |
I think there may be an issue with file permission on Windows that only happens when updating from frozen app as I couldn't reproduce it while simulating an update from codes. |
This issue happens here as well. Windows 7 x64. |
The problem is that: but the app-0.2.win32 folder is actually nested into a 'appdata' folder, so that's the right source path: if you modify the paths manually before the _do_MOVE_FROM task, and turn off md5 hash checking, everything works. |
An easier solution: MD5 hash checking still fails. when turned off, everything works. |
I logged the MD5 hashes of each file, and found that the root Could someone else look up into it? It seems to be the limit of my knowledge... Thanks. |
…atrix#47 Update fails during second update requiring admin rights under Windowssaf
…atrix#47 Update fails during second update requiring admin rights under Windowssaf
…atrix#47 Update fails during second update requiring admin rights under Windowssaf
My application could not update without downloading the whole zip file and that happened only when the second update applied on Windows (no problem on Ubuntu and Mac OS X).
The first version, 1.0.1, was updated successfully from appname-1.0.2.win32.from-1.0.1.patch, but after that the app failed to update with appname-1.0.3.win32.from-1.0.2.patch and could be updated only after downloading the whole .zip file (around 13 MB).
If I re-installed application, it would be happily to update from 1.0.1 to 1.0.3 without the .zip file download. Yet, problem reappears when 1.0.4 patch to be applied subsequently.
The text was updated successfully, but these errors were encountered: