Homebrew / homebrew-cask

🍻 A CLI workflow for the administration of macOS applications distributed as binaries
https://brew.sh
BSD 2-Clause "Simplified" License
20.85k stars 10.68k forks source link

Bug report: Brew cask install fails with undefined method `version' for Hbc::MacOS:Module #23397

Closed Samze closed 8 years ago

Samze commented 8 years ago

Description of issue

When trying to install to run the command brew cask install lastpass

I get the following error: Error: Download failed on Cask 'lastpass' with message: undefined method``version' for Hbc::MacOS:Module

Any help would be greatly appreciated.

Output of `brew cask install lastpass --verbose` ``` β—‹ β†’ brew cask install lastpass --verbose Warning: The default Caskroom location has moved to /usr/local/Caskroom. Please migrate your Casks to the new location and delete /opt/homebrew-cask/Caskroom, or if you would like to keep your Caskroom at /opt/homebrew-cask/Caskroom, add the following to your HOMEBREW_CASK_OPTS: --caskroom=/opt/homebrew-cask/Caskroom For more details on each of those options, see https://github.com/caskroom/homebrew-cask/issues/21913. ==> Downloading https://lastpass.com/download/cdn/lpmacosx.zip Error: Download failed on Cask 'lastpass' with message: undefined method `version' for Hbc::MacOS:Module Error: Kernel.exit ```
Output of `brew doctor` ``` Please note that these warnings are just used to help the Homebrew maintainers with debugging if you file an issue. If everything you use Homebrew for is working fine: please don't worry and just ignore them. Thanks! Warning: Your XQuartz (2.7.7) is outdated Please install XQuartz 2.7.8: https://xquartz.macosforge.org Warning: You have unlinked kegs in your Cellar Leaving kegs unlinked can lead to build-trouble and cause brews that depend on those kegs to fail to run properly once built. Run `brew link` on these: ctags Warning: Broken symlinks were found. Remove them with `brew prune`: /usr/local/bin/npm-install-missing Warning: Some keg-only formula are linked into the Cellar. Linking a keg-only formula, such as gettext, into the cellar with `brew link ` will cause other formulae to detect them during the `./configure` step. This may cause problems when compiling those other formulae. Binaries provided by keg-only formulae may override system binaries with other strange results. You may wish to `brew unlink` these brews: homebrew/dupes/libiconv ```
Output of `brew cask doctor` ``` β—‹ β†’ brew cask doctor ==> macOS Release: 10.11 ==> macOS Release with Patchlevel: 10.11.6 ==> Hardware Architecture: intel-64 ==> Ruby Version: 2.0.0-p648 ==> Ruby Path: /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby ==> Homebrew Version: Homebrew 0.9.5 (git revision f01e3; last commit 2016-01-29) ==> Homebrew Executable Path: /usr/local/bin/brew ==> Homebrew Cellar Path: /usr/local/Cellar ==> Homebrew Repository Path: /usr/local ==> Homebrew Origin: http://github.com/Homebrew/homebrew.git ==> Homebrew-cask Version: 0.60.0 (git revision 6767; last commit 3 hours ago) ==> Homebrew-cask Install Location: Warning: The default Caskroom location has moved to /usr/local/Caskroom. Please migrate your Casks to the new location and delete /opt/homebrew-cask/Caskroom, or if you would like to keep your Caskroom at /opt/homebrew-cask/Caskroom, add the following to your HOMEBREW_CASK_OPTS: --caskroom=/opt/homebrew-cask/Caskroom For more details on each of those options, see https://github.com/caskroom/homebrew-cask/issues/21913. ==> Homebrew-cask Staging Location: /opt/homebrew-cask/Caskroom ==> Homebrew-cask Cached Downloads: /Library/Caches/Homebrew/Cask 0 files, 0B ==> Homebrew-cask Default Tap Path: /usr/local/Library/Taps/caskroom/homebrew-cask ==> Homebrew-cask Alternate Cask Taps: ==> Homebrew-cask Default Tap Cask Count: 3272 ==> Contents of $LOAD_PATH: /usr/local/Library/Taps/caskroom/homebrew-cask/lib /usr/local/Library/Homebrew /Library/Ruby/Site/2.0.0 /Library/Ruby/Site/2.0.0/x86_64-darwin15 /Library/Ruby/Site/2.0.0/universal-darwin15 /Library/Ruby/Site /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0 /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/x86_64-darwin15 /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/universal-darwin15 /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0 /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/x86_64-darwin15 /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/universal-darwin15 ==> Contents of $RUBYLIB Environment Variable: ==> Contents of $RUBYOPT Environment Variable: ==> Contents of $RUBYPATH Environment Variable: ==> Contents of $RBENV_VERSION Environment Variable: ==> Contents of $CHRUBY_VERSION Environment Variable: ==> Contents of $GEM_HOME Environment Variable: ==> Contents of $GEM_PATH Environment Variable: ==> Contents of $BUNDLE_PATH Environment Variable: ==> Contents of $PATH Environment Variable: PATH="/Users/pairingstation3/.rbenv/shims:/Users/pairingstation3/.rbenv/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/X11/bin:/Applications/IBM/MobileFirst-CLI:/usr/local/garage/bin:/Users/pairingstation3/go/bin:/usr/local/opt/go/libexec/bin:/usr/local/script:/usr/local/Library/Taps/caskroom/homebrew-cask/cmd:/usr/local/Library/ENV/scm" ==> Contents of $SHELL Environment Variable: SHELL="/bin/bash" ==> Contents of Locale Environment Variables: LANG="en_GB.UTF-8" ==> Running As Privileged User: No ```
zimolzak commented 8 years ago

πŸ‘ Same error with brew cask install osxfuse. As suggested here: https://github.com/gittup/tup/issues/204 because tup depends on osxfuse....

jawshooah commented 8 years ago

==> Homebrew Version: Homebrew 0.9.5 (git revision f01e3; last commit 2016-01-29)

@Samze Why is your Homebrew so outdated? Have you run brew update recently?

jawshooah commented 8 years ago

More to the point, did you not follow the pre-bug-report guide, which instructs you to do just that (and a bit more) before reporting an issue?

jawshooah commented 8 years ago

@zimolzak I can't debug your issue unless you provide the same amount of verbose output as @Samze has.

adidalal commented 8 years ago

Please always follow the reporting bugs guide. To do so, edit the top post and then comment after this one so I can check back.

Closing in the meantime, because a number of people never report back and it’s useless to keep the issue open in that case and without all the required information.