homebrew-bundle: Unknown command: bundle

Seeing this in our CI right now:

+ export HOMEBREW_BUNDLE_NO_LOCK=1
+ HOMEBREW_BUNDLE_NO_LOCK=1
+ brew bundle check --no-upgrade
==> Tapping homebrew/bundle
Cloning into '/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle'...
remote: Enumerating objects: 93, done.
remote: Counting objects: 100% (93/93), done.
remote: Compressing objects: 100% (84/84), done.
remote: Total 93 (delta 4), reused 34 (delta 2), pack-reused 0
UnpacUnpacking objects: 100% (93/93), done.
Tapped (192 files, 262.8KB).
Error: Unknown command: bundle
+ brew bundle --no-upgrade
Error: Unknown command: bundle

I suspect it has something to do with the PR that was just merged #643 ?

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 1
Comments: 16 (5 by maintainers)

Commits related to this issue

Fix macOS travis build Works around https://github.com/Homebrew/homebrew-bundle/issues/646 — committed to glebm/devilutionX by glebm 4 years ago
Travis: Update osx_image to fix build Works around https://github.com/Homebrew/homebrew-bundle/issues/646 — committed to glebm/devilutionX by glebm 4 years ago
Fix macOS travis build Works around https://github.com/Homebrew/homebrew-bundle/issues/646 — committed to diasurgical/devilutionX by glebm 4 years ago
TravisCI: Fix build error due to outdate Homebrew See: - https://github.com/Homebrew/homebrew-bundle/issues/646 - https://travis-ci.community/t/macos-build-fails-because-of-homebrew-bundle-unknown-co... — committed to carobim/carob by pmer 4 years ago

Most upvoted comments

Would be nice also to get a deprecation notice from the software tools before functionality gets removed and things start breaking.

No, sorry, you’ve misunderstood how this works:

Homebrew (except for the package manager itself in Homebrew/brew) is a rolling release package manager which auto-updates by default so everyone is on the latest master branch of all repositories
Travis CI have disabled this functionality for all taps and Homebrew itself
They do not include e.g. brew bundle in their image at a supported version
When you brew tap in their unsupported configuration (it normally auto-updates) you end up on the latest version of a tap which will likely fail

I’m not sure how we can really address this beyond “don’t allow people with auto-update disabled to tap new taps” which will break things even further for Travis CI users (but perhaps is warranted).

Thanks for all your work on this project!

Thanks for your kind words: they are genuinely appreciated.

MikeMcQuaid on Feb 21, 2020

Adding update: true to my .travis.yml (documented here) did solve the problem. It sounds like Homebrew Bundle now depends on a newer version of Homebrew than the one included on the Travis CI VM?

jablko on Feb 20, 2020

I opened a macOS Packer Templates PR to add Homebrew Bundle to the macOS images. Does that look right?

Have commented, thanks! Beyond that I’m not sure I know enough about Travis to help further.

MikeMcQuaid on Feb 22, 2020