BREW INSTALL SMARTSVN UPGRADE
So, for some reason, that brew upgrade invocation upgraded the cask. When you ran brew update, you may have updated the local cask tap to a state that included sublime-text 4.121. I wonder if the cause was actually just a weird timing bug. If you choose to do this, we may need to continue working to try to figure out why brew upgrade isn't operating as expected.
BREW INSTALL SMARTSVN UPDATE
If you don't have a ton of disk space and feel strongly about using HOMEBREW_INSTALL_FROM_API (or aren't planning on contributing in the future), then you can keep HOMEBREW_INSTALL_FROM_API set, untap homebrew/core and homebrew/cask, and use brew update to update Homebrew in the future instead of brew update-reset. More information about this can be found in the docs and in each repository's CONTRIBUTING.md file. That way, when you're done, you can simply re-checkout the master branch and run brew update to get the latest changes on the developer track. As you develop, I would highly recommend using the developer commands brew bump-formula-pr and brew bump-cask-pr when making simple version bump PRs, and doing this development on separate branches. This will mean, though, that you won't be able to use HOMEBREW_INSTALL_FROM_API. If you want to continue to contribute to homebrew/core or homebrew/cask, it's best if you enable developer mode (by running brew developer on or any developer command). This should have been documented but wasn't, so I've added it in #12333. HOMEBREW_INSTALL_FROM_API isn't supposed to be used by Homebrew developers/contributors because many developer commands require homebrew/core and/or homebrew/cask to be cloned locally. It seems that something is odd about the setup that you have, and I think it's because you've done some Homebrew development before but, for whatever reason, developer mode was never enabled (or was manually disabled). It's very late for me so I need to go to sleep, but here are my final thoughts. opt/homebrew/Library/Homebrew/brew.rb:147:in `'
opt/homebrew/Library/Homebrew/cmd/doctor.rb:57:in `doctor' opt/homebrew/Library/Homebrew/cmd/doctor.rb:57:in `each' opt/homebrew/Library/Homebrew/cmd/doctor.rb:64:in `block in doctor' opt/homebrew/Library/Homebrew/diagnostic.rb:594:in `check_coretap_integrity' opt/homebrew/Library/Homebrew/diagnostic.rb:162:in `broken_tap' opt/homebrew/Library/Homebrew/tap.rb:137:in `remote' usr/bin/swift /opt/homebrew/Library/Homebrew/cask/utils/quarantine.swift => Checking check_cask_quarantine_support => Checking check_cask_environment_variables opt/homebrew/Library/Homebrew/shims/shared/git -version I don't have the ability to test on either of these machines, but I'll see if another maintainer can help check. I'm on an Intel machine running Big Sur, I wonder if it's related to either being on Monterey or ARM (if I had to bet I'd guess the latter would be more problematic). (736 files, 8.5MB) => Caveats => you-get To use post-processing options, run `brew install ffmpeg` or `brew install libav`. => Summary 🍺 /usr/local/Cellar/you-get/_1: 736 files, 8.5MB Removing: /usr/local/Cellar/you-get/. (3 files, 208.4KB) => Upgrading you-get -> _1 => Pouring you-get-_1.big_ => Caveats To use post-processing options, run `brew install ffmpeg` or `brew install libav`.
🍺 /usr/local/Cellar/ca-certificates/: 3 files, 208.4KB Removing: /usr/local/Cellar/ca-certificates/. $ HOMEBREW_DEVELOPER= HOMEBREW_INSTALL_FROM_API= "1 " brew upgrade => Downloading Already downloaded: /Users/rylanpolster/Library/Caches/Homebrew/downloads/.gz => Downloading Already downloaded: /Users/rylanpolster/Library/Caches/Homebrew/downloads/4d8a9ec93218d1bda9a27cb52aa372a6926f4d01c1cd59020948681ff67d828c-you-get-_1.big_ => Downloading Already downloaded: /Users/rylanpolster/Library/Caches/Homebrew/downloads/.gz => Upgrading 2 outdated packages: ca-certificates -> you-get -> _1 => Upgrading ca-certificates -> => Pouring .gz => Regenerating CA certificate bundle from keychain, this may take a while.
0 kommentar(er)
