-
-
Notifications
You must be signed in to change notification settings - Fork 10.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
Cask LuLu: problem with update logic #166180
Comments
Is there an ongoing issue with the way |
@bevanjkay - yeah there is an issue still. It didn't wipe my configuration that I could find, but it tried to run an uninstall which failed on ARM due to "bad CPU type in executable" as the uninstaller is an x86_64 specific binary. I started some time ago to rewrite the uninstall logic into a So I think there's something here to fix, but part of it is certainly upstream in adding ARM support for the uninstall / upgrade binary. |
@krehel But we aren't running any uninstaller anymore. What you are seeing is a leftover from the previous version of the caskfile. |
Since The upgrade for cask LuLu as from the maintainer should be as simple as quit the app and replace it. upgrade script: {
executable: "#{staged_path}/LuLu.app/Contents/MacOS/LuLu",
args: ["-upgrade"],
sudo: true,
} The problem is that even if LuLu maintainer has added support for other CLI args, the useful script for uninstall is always the same problem if uninstall script: {
executable: "#{staged_path}/LuLu.app/Contents/MacOS/LuLu",
args: [“-uninstall"],
sudo: true,
} |
This happened twice in the past week
Both of which we shouldn't be running the uninstall, I agree. But yet it still seemed to trigger. Unless I need to do a complete removal and reinstall to reset something? |
That seems weird. |
The current caskfile does not do anything when upgrading or uninstalling except remove the There would be more than a handful of apps that provide an "uninstaller" that we don't use because generally speaking, the So we could try to replicate as much logic from the upstream uninstaller as possible to the It is currently not possible to run the uninstaller in the |
I'd say also there's different issues at play here. Mine is assuredly an upstream issue as the uninstall needs to be compiled for ARM, I'm just thinking of workarounds. |
I don’t know what’s happening to you, I don’t have any issue on uninstalling it via Homebrew on ARM. |
That adds another twist for me at least. I wonder if when trying to debug this uninstall issue sometime ago I accidentally installed the intel version. Thanks for the data point on that. I'll investigate my own issue. |
@krehel maybe, or double check if you made some change to your local tap and you’re using that for LuLu cask installs and update with |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Not happening lately with last updates. |
Verification
--force
.brew update-reset && brew update
and retried my command.brew doctor
, fixed as many issues as possible and retried my command.Description of issue
Like in previous issues about cask LuLu, there are some issues on upgrading the cask.
As reported from an Homebrew mantainer,
brew upgrade <cask_name>
runsbrew uninstall <cask_name> && brew install <cask_name>
.From previous commit was added the uninstall script but then removed since it creates problem if running
brew upgrade
.As reported from the cask mantainer the logic of upgrade and uninstall are really different for the cask, since the uninstall script run by the app on uninstall process removes files/rules on its own.
LuLu creator now has added support for different CLI-commands arguments like {
-uninstall
,-upgrade
,-install
} but it seems to me that they can’t be used since only auninstall
stanza is available for homebrew-casks.Are there any workaround to avoid
brew uninstall
onbrew upgrade
or anything else in this case?Command that failed
brew upgrade LuLu
Output of command with
--verbose --debug
`brew upgrade` usually works, the problem is the result of upgrading the cask.
Output of
brew doctor
andbrew config
Output of
brew tap
The text was updated successfully, but these errors were encountered: