-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Command ran by the RPM updater not working #8305
Comments
(sorry, the |
That's very interesting! Would you be willing to open up a PR with that change? |
Stop uninstalling an app before it updates, as dnf, yum, and zypper all support updating an app from a .rpm, and because app.getName() returns the product name of the app instead of its package name. (electron-userland#8305)
Stop uninstalling an app before it updates, as dnf, yum, and zypper all support updating an app from a .rpm, and because app.getName() returns the product name of the app instead of its package name. (electron-userland#8305)
PR: #8311 |
Stop uninstalling an app before it updates, as dnf, yum, and zypper all support updating an app from a .rpm, and because app.getName() returns the product name of the app instead of its package name. (Fixes #8305)
24.13.3 (electron-updater 6.2.1)
20.15.0
31.1.0
current
RPM
When an app from an RPM file updates, the command that electron-updater runs tries to uninstall the app by its name, then installs the new version's RPM file. However, (with the dnf package manager for example) it is not possible to do this, as we need the app's package name to uninstall it. On Electron apps it seems to be the
name
value in our package.json, but electron-updater tries to do this with theproductName
value from our electron-builder config.So, the app just restarts on the same version and causes a bootloop if updates are on start, automatic and forced.
(I also do not understand the need to uninstall the app before installing the new version, as dnf, yum, and zypper all support updating apps from RPM files.)
The text was updated successfully, but these errors were encountered: