Skip to content
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

Allow --package-file arg to escape spaces in filenames #2739

Merged
merged 1 commit into from
Mar 25, 2018

Conversation

jonzlin95
Copy link
Contributor

Right now package file doesn't escape spaces in the filename, which causes a bug where the package file passed to the nsis installer to be incorrect. This means that when the installer runs, it will fail on folders such as

C:\Users\first last\appdata\roaming\package-version.7z

This issue only seems to occur upon a failed Differential update (due to perMachine) followed by a full download to the users' appdata folder.

This fixes it by forcing the whole file path to be a single arg. I believe this also fixes the following issue

#2640

I'm unsure if #2363 is the same issue, but I see similar symptoms

Right now package file doesn't escape spaces in the filename, which causes a bug where the package file passed to the nsis installer to be incorrect. This means that when the installer runs, it will fail on folders such as 

`C:\Users\first last\appdata\roaming\package-version.7z`

This fixes it by forcing the whole file path to be a single arg.
@develar develar merged commit 24a585b into electron-userland:master Mar 25, 2018
@develar
Copy link
Member

develar commented Mar 25, 2018

I doubt that it fixed mentioned issues — fix doesn't related to permissions. Anyway — thanks a lot, it may be a part of existing issues.

@jonzlin95
Copy link
Contributor Author

It did fix the first one, because it was a misdiagnose on my end. I can look into fixing other ones with similar issues since I’ve gone through all the Nsis code and also through most of the update code

@jonzlin95
Copy link
Contributor Author

@develar -> I was investigating this some more, and I noticed the permissions issue is related somehow to the oneClick setting. Haven't had lot of time to kind of dig through outside of the day job, but the fix above only worked on assistedInstaller, but not on oneClick. Will keep updates on this thread.

@develar
Copy link
Member

develar commented Mar 26, 2018

Probably you are right — we pass args to elevate and so.. yeach. Thanks a lot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants