MacOS build fails because of homebrew "bundle" unknown command

Same here.

Short web search told me that homebrew bundle has been announced as deprecated – it seems to have vanished now. I do not use macOS personally, but offering support for it would be quite nice. Thanks in advance!

Seems like this commit:

broke the installation of that tap. In order to provide external commands (like brew bundle) Homebrew expects a file brew-bundle.rb, which has been deleted from the repo (or renamed bundle.rb

From this issue: it seems like brew update might fix the issue. Would be nice if the Travis team could update the build image, rather than requiring us to run brew update on every build. As you note in your docs:

By default, the Homebrew addon will not run brew update before installing packages. brew update can take a long time and slow down your builds.

edit: confirming that adding update: true fixes my build.

        - graphicsmagick
        update: true

Can you provide a link to the deprecation announcement? I can’t find that anywhere.

I stumbled over this SO question, which points to this issue. Just realized, however, that those links are quite dated.

Thanks a lot!

update: true

works for me as well. Takes a while, though, but at least the build runs now.

1 Like

How frequently do the macOS virtual machines receive updates?

My understanding is that Homebrew Bundle, which the Homebrew addon uses, now depends on Homebrew 2.2.5, and the macOS virtual machines currently ship an older version.

Until the virtual machines receive an update, or something else changes, the workaround is to update it via update: true, as above.


I opened a macOS Packer Templates PR to add Homebrew Bundle to the macOS images and avoid mismatches between the installed (stale) version of Homebrew and latest version of Homebrew Bundle.


They say they are thinking about it, but not very hard apparently:


I also have the same issue with many of my projects:

We have the same problem too:

Add update: true under the homebrew: key in your environment.

Thanks to @BanzaiMan. Also see OS X image and “Error: Unknown command: bundle” and MacOS build fails because of homebrew “bundle” unknown command.

@BanzaiMan Can we expect an updated macOS image in coming days to solve this? Having Homebrew updated to a current functional version directly in the image should reduce build times for all of us who currently had to resort to forcing update: true in our builds.

1 Like

The new image is available:

1 Like

Confirmed fix for OSX 10.12-10.14 (Homebrew currently supports 10.13+)
See MacOS build fails because of homebrew "bundle" unknown command.

1 Like

I think it’s a misinformed that it’s fixed for OS X 10.12-10.14, but rather Xcode of the mentioned version–only macOS 10.14 is fixed.

1 Like

I still get the error, and adding update: true comes with a few minutes penalty :frowning:

@elichai2 Please link to a build showcasing the problem. I may very well be something different.

Here is the exact error:

I’m using xcode10.1 because that’s the latest valgrind currently supports.

Now with update: true that doesn’t fail anymore:

1 Like

Confirmed the problem for xcode10.x.
It turns out that MacOS build fails because of homebrew "bundle" unknown command is accurate and indeed, they only updated xcode11.x.

In my previous test, the command actually failed, but that failure was ignored and it exited with 0 (which is a bug in and of itself) – so I didn’t notice that.

How can we get someone to fix this?
I’m using xcode 10.x Because I need valgrind and it currently only supports up to macOS 10.13.
Maybe I should go back to xcode 9.x?