-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Calling brew cask install is disabled! Use brew install [--cask] instead. #1524
Comments
Files identified in the description: If these files are inaccurate, please update the |
Note: I've commented here about this issue. It's not helpful that the Homebrew folks have decided against maintaining a stable command-line interface. It would be worth checking for other Homebrew subcommands that may be in deprecated state since those changes will create similar problems. |
There's probably more to do, but these quick local edits (patch file below) seem to have things working as expected for me.
|
tl;dr: The recent homebrew 2.7 release broke the |
Was able to get it working again by downgrading and locking Homebrew to
|
There's already a PR for this: #1481 Since you are Homebrew users, would be great if you could test it! |
(Also, I'm quite confused why |
Files identified in the description: If these files are inaccurate, please update the |
Well, from looking at the commit history, the |
Response from the Homebrew team: |
Ok, so it was indeed just deprecated a few days ago (December 1st), and got removed only since yesterday. So talking about it as deprecated was actually correct until the day before yesterday :) |
Hi there, Homebrew maintainer here. I can clear up a few things:
The alternative to I'm not much of an ansible user but I'm happy to try and help out if needed. Feel free to point me in the right direction if anything is blocked and could use feedback from the Homebrew side of things. |
Thank you @Rylan12! |
Very helpful @raymondyou97 Thanks. |
…o and we're just waiting for Ansible 2.10.5 to get pushed out. ansible-collections/community.general#1524
SUMMARY
I have a simple playbook that ensures a set of brew casks are installed. It stopped working this morning (actually, probably three days ago with this merge) because, apparently, the Homebrew folks disabled
brew cask install
. I'm submitting this as a bug report because I imagine it affects everyone using thehomebrew_cask
module. Cask installation is no longer possible withhomebrew_cask
until this issue is resolved.ISSUE TYPE
COMPONENT NAME
homebrew_cask
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
STEPS TO REPRODUCE
Create a simple inventory playbook to ensure that the "docker" cask is installed locally.
EXPECTED RESULTS
Since I already have this cask installed, I expect Ansible to report that no change was required.
ACTUAL RESULTS
The play fails with this stack trace:
ADDITIONAL COMMENTS
I can easily reproduce this error by running the following command:
The solution seems to be to use a command-line like this instead:
TRYING community.general.homebrew
I tried to do the same thing with the
homebrew
module, but the idempotency check fails because the--cask
option is required for bothlist
andinstall
for casks:I've not studied the code in the
homebrew
module, but I imagine it checks for installation by doing something like this:For casks, it needs to do this:
I can work around this idempotency issue by adding another task to check if docker is installed first, but that's messy. This check should really be handled by the module.
The text was updated successfully, but these errors were encountered: