brew config output

HOMEBREW_VERSION: 2.7.6-11-g5b2f8a5 ORIGIN: https://github.com/Homebrew/brew HEAD: 5b2f8a5a7307b58843eedfb2886a80964b937b30 Last commit: 4 weeks ago Core tap ORIGIN: https://github.com/Homebrew/homebrew-core Core tap HEAD: 1fe981399a12641c22ac4860928e762c1d61236c Core tap last commit: 4 weeks ago Core tap branch: master HOMEBREW_PREFIX: /usr/local HOMEBREW_CASK_OPTS: [] HOMEBREW_EDITOR: nvim HOMEBREW_MAKE_JOBS: 8 HOMEBREW_NO_AUTO_UPDATE: set HOMEBREW_NO_INSTALL_CLEANUP: set Homebrew Ruby: 2.6.3 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3_2/bin/ruby CPU: octa-core 64-bit kabylake Clang: 11.0 build 1103 Git: 2.30.0 => /usr/local/bin/git Curl: 7.64.1 => /usr/bin/curl macOS: 10.15.7-x86_64 CLT: 1103.0.32.62 Xcode: 12.4

brew doctor output

Your system is ready to brew.

• [X] The brew doctor above contains no "Warning" lines.

What were you trying to do (and why)?

We run brew bump-formula-pr in our CI. Without any changes to our brew process, it started failing on Feb 20 (the last working run was Jan 23) with the error message "Error: This formula is not a tap!"

What happened (include all command output)?

Error: This formula is not in a tap!
Warning: Attempt 1 failed. Reason: Child_process exited with error code 1
git config --replace-all homebrew.devcmdrun true
Error: This formula is not in a tap!
Warning: Attempt 2 failed. Reason: Child_process exited with error code 1
git config --replace-all homebrew.devcmdrun true
Error: This formula is not in a tap!
Warning: Attempt 3 failed. Reason: Child_process exited with error code 1
git config --replace-all homebrew.devcmdrun true
Error: This formula is not in a tap!
Warning: Attempt 4 failed. Reason: Child_process exited with error code 1
git config --replace-all homebrew.devcmdrun true
Error: This formula is not in a tap!
Warning: Attempt 5 failed. Reason: Child_process exited with error code 1
git config --replace-all homebrew.devcmdrun true
Error: This formula is not in a tap!

What did you expect to happen?

I expect to be able to run brew bump-formula-pr on a local repo to update the formula file for processing (opening a PR or making a commit).

Step-by-step reproduction instructions (by running brew commands)

brew bump-formula-pr "Formula/${FORMULA_NAME}.rb" --url (pypi url here) --sha256 (sha goes here) --version=$PYPI_VERSION --no-audit --write --commit --force --verbose

We've gotten the same result in our CI (output) and on a local machine.

<!-- #review-period-begin -->

Review period will end on 2021-03-02 at 00:00:00 UTC.

This is needed to build glibc on CI

• [ ] Have you followed the guidelines in our Contributing document?
• [ ] Have you checked to ensure there aren't other open Pull Requests for the same change?
• [ ] Have you added an explanation of what your changes do and why you'd like us to include them?
• [ ] Have you written new tests for your changes? Here's an example.
• [ ] Have you successfully run brew style with your changes locally?
• [ ] Have you successfully run brew typecheck with your changes locally?
• [ ] Have you successfully run brew tests with your changes locally?

As titled, I copied the logic from homebrew installation script.

As titled, it's no longer required to tap homebrew/cask to install apps from homebrew-casks.

Completions are auto-generated upon running brew man, so any change you'd like to propose should be in these files instead.

Is there a way now to allow specific Gems which are not in the Gemfile? The cask review action broke because it cannot load the git_diff gem.

Provide a detailed description of the proposed feature

I believe that 'brew upgrade' cask shell completions should suggest casks from the greedy list of outdated casks.

PR: https://github.com/Homebrew/brew/pull/10730

What is the motivation for the feature?

My reasoning is that when you are using an explicit upgrade command for a certain cask you are showing an intention to really upgrade it, so suggestions from the greedy outdated casks list should be used.

How will the feature be relevant to at least 90% of Homebrew users?

All Homebrew users using the shell completion functionality will see the benefit of this change when using completion with 'brew upgrade' command for casks.

What alternatives to the feature have been considered?

I can't think of any alternatives.

• [x] Have you followed the guidelines in our Contributing document?
• [x] Have you checked to ensure there aren't other open Pull Requests for the same change?
• [x] Have you added an explanation of what your changes do and why you'd like us to include them?
• [n/a] Have you written new tests for your changes? Here's an example.
• [x] Have you successfully run brew style with your changes locally?
• [x] Have you successfully run brew typecheck with your changes locally?
• [x] Have you successfully run brew tests with your changes locally?

I believe that cask upgrade completions should suggest casks from the greedy list of outdated casks. My reasoning is that when you are using an explicit upgrade command for a certain cask you are showing an intention to really upgrade it, so suggestions from the greedy outdated casks list should be used.

• [x] Have you followed the guidelines in our Contributing document?
• [x] Have you checked to ensure there aren't other open Pull Requests for the same change?
• [x] Have you added an explanation of what your changes do and why you'd like us to include them?
• [ ] Have you written new tests for your changes? Here's an example.
• [x] Have you successfully run brew style with your changes locally?
• [x] Have you successfully run brew typecheck with your changes locally?
• [x] Have you successfully run brew tests with your changes locally?

This is breaking netris.

brew config output

$ brew config HOMEBREW_VERSION: 3.0.2-104-g4d88d10 ORIGIN: https://github.com/Homebrew/brew HEAD: 4d88d100499d5ccf389e9725ef7f20de410e8b02 Last commit: 87 minutes ago Core tap ORIGIN: https://github.com/Homebrew/homebrew-core Core tap HEAD: 466697a76b4dfddf9314b2ca791a5c733c797087 Core tap last commit: 12 minutes ago Core tap branch: master HOMEBREW_PREFIX: /opt/homebrew HOMEBREW_CASK_OPTS: [] HOMEBREW_EDITOR: vim HOMEBREW_GITHUB_API_TOKEN: set HOMEBREW_MAKE_JOBS: 8 HOMEBREW_NO_ANALYTICS: set HOMEBREW_NO_AUTO_UPDATE: set Homebrew Ruby: 2.6.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby CPU: octa-core 64-bit arm_firestorm_icestorm Clang: 12.0 build 1200 Git: 2.30.1 => /opt/homebrew/bin/git Curl: 7.64.1 => /usr/bin/curl macOS: 11.2.1-arm64 CLT: 12.4.0.0.1.1610135815 Xcode: N/A Rosetta 2: false

brew doctor output

$ brew doctor Your system is ready to brew.

• [X] The brew doctor above contains no "Warning" lines.

What were you trying to do (and why)?

Install kubectx on Apple Silicon

What happened (include all command output)?

$ HOMEBREW_DEVELOPER= brew install kubectx ==> Cloning https://github.com/kubernetes/kubernetes.git Updating /Users/dustin/Library/Caches/Homebrew/kubernetes-cli--git ==> Checking out tag v1.20.4 HEAD is now at e87da0bd Release commit for Kubernetes v1.20.4 HEAD is now at e87da0bd Release commit for Kubernetes v1.20.4 ==> Downloading https://github.com/ahmetb/kubectx/archive/v0.9.3.tar.gz ==> Downloading from https://codeload.github.com/ahmetb/kubectx/tar.gz/v0.9.3 ######################################################################## 100.0% ==> Installing dependencies for kubectx: kubernetes-cli ==> Installing kubectx dependency: kubernetes-cli ==> make WHAT=cmd/kubectl

$ HOMEBREW_DEVELOPER= brew install kubernetes-cli Error: kubernetes-cli: no bottle available! You can try to install from source with: brew install --build-from-source kubernetes-cli Please note building from source is unsupported. You will encounter build failures with some formulae. If you experience any issues please create pull requests instead of asking for help on Homebrew's GitHub, Twitter or any other official channels.

What did you expect to happen?

I expected brew install kubectx to fail to install because it had an unbottled dependency of kubernetes-cli instead of trying to build the dependency from source. When directly trying to install kuberntes-cli, it refuses to install or build from source as expected.

Step-by-step reproduction instructions (by running brew commands)

brew install kubectx

<!-- #review-period-end -->

Review period skipped due to critical label.

• [x] Have you followed the guidelines in our Contributing document?
• [x] Have you checked to ensure there aren't other open Pull Requests for the same change?
• [x] Have you added an explanation of what your changes do and why you'd like us to include them?
• [ ] Have you written new tests for your changes? Here's an example.
• [x] Have you successfully run brew style with your changes locally?
• [x] Have you successfully run brew typecheck with your changes locally?
• [x] Have you successfully run brew tests with your changes locally?

This is breaking netris.

On installation curl -fsSL -o install.sh https://raw.githubusercontent.com/Homebrew/install/master/install.sh

I get this error

HEAD is now at 4d88d1004 Merge pull request #10726 from Bo98/gem-path-no-env error: Not a valid ref: refs/remotes/origin/master fatal: ambiguous argument 'refs/remotes/origin/master': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]'

• [x] Have you followed the guidelines in our Contributing document?
• [x] Have you checked to ensure there aren't other open Pull Requests for the same change?
• [x] Have you added an explanation of what your changes do and why you'd like us to include them?
• [ ] Have you written new tests for your changes? Here's an example.
• [x] Have you successfully run brew style with your changes locally?
• [x] Have you successfully run brew typecheck with your changes locally?
• [x] Have you successfully run brew tests with your changes locally?

I think I've covered everything now.

<!-- #review-period-end -->

Review period skipped due to critical label.

<!-- #review-period-end -->

Review period skipped due to critical label.

• [x] Have you followed the guidelines in our Contributing document?
• [x] Have you checked to ensure there aren't other open Pull Requests for the same change?
• [x] Have you added an explanation of what your changes do and why you'd like us to include them?
• [ ] Have you written new tests for your changes? Here's an example.
• [x] Have you successfully run brew style with your changes locally?
• [x] Have you successfully run brew typecheck with your changes locally?
• [x] Have you successfully run brew tests with your changes locally?

I think I've covered everything now.

• [x] Have you followed the guidelines in our Contributing document?
• [x] Have you checked to ensure there aren't other open Pull Requests for the same change?
• [x] Have you added an explanation of what your changes do and why you'd like us to include them?
• [ ] Have you written new tests for your changes? Here's an example.
• [x] Have you successfully run brew style with your changes locally?
• [x] Have you successfully run brew typecheck with your changes locally?
• [x] Have you successfully run brew tests with your changes locally?

This prevents the ENV bleeding into child processes, such as system Ruby scripts invoked from formulae.