Closed hakamadare closed 8 years ago
Yeah. Appears homebrew has split up formulae from the package manager itself (a change I am quite happy to see!) but we'll want to fix a few things on boxen's side for compatibility with the new world order.
Sent from my iPhone
On Apr 4, 2016, at 9:30 AM, Steve Huff notifications@github.com wrote:
After upgrading homebrew to the latest version (apparently over the past weekend the maintainers split it into Homebrew/brew and Homebrew/homebrew-core?), I now get the following Puppet error when running boxen:
Debug: Executing 'brew update' Error: Execution of 'brew update' returned 1: Error: Cowardly refusing to 'sudo brew update' You can use brew with sudo, but only if the brew executable is owned by root. However, this is both not recommended and completely unsupported so do so at your own risk. Error: /Stage[main]/Homebrew::Repo/Homebrew_repo[/opt/boxen/homebrew]/min_revision: change from 342ed4c830e349efee4cf4719d44eae96112cd47 to e90b6e9ded2fd2c73a4e0d93f5dbc5b075a61b7c failed: Execution of 'brew update' returned 1: Error: Cowardly refusing to 'sudo brew update' You can use brew with sudo, but only if the brew executable is owned by root. However, this is both not recommended and completely unsupported so do so at your own risk. Looks like something has changed upstream? attn @jacobbednarz who seems to be working on something related
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub
Yep! I'm tackling a short term fix at https://github.com/boxen/puppet-homebrew/pull/92 and once we get everyone working again, I'll take a look at getting it working using the split repository setup.
Made a release in https://github.com/boxen/puppet-homebrew/releases/tag/2.0.1.
@mikemcquaid thanks for that! i just modified my Puppetfile to pull puppet-homebrew 2.0.1 (and have confirmed that there's a 2.0.1 module downloaded by librarian-puppet), but i still see the same error message; is there something else i need to do to implement the short term fix?
I'll be updating our-boxen shortly with 2.0.1 if you'd like to test that out?
@hakamadare I haven't personally investigated this. It may need a more involved fix. I'm not personally using Boxen any more but if people are still struggling in a few days I can try and boot up a VM and check it out.
@hakamadare check out #815 as the proposed fix. You should be able to checkout this branch locally and run boxen
with a working homebrew again.
Made another release in https://github.com/boxen/puppet-homebrew/releases/tag/2.0.2.
This fixes it for me. Going to send a pull request over to our-boxed as it's currently pegged to the old (now breaking) 2.0.1
@snewman I've got one open via #816 however I before merging I was interested in the reasoning behind why using root has all of a sudden broke.
Ah, gotcha! On Tue, 5 Apr 2016 at 11:05, Jacob Bednarz notifications@github.com wrote:
@snewman https://github.com/snewman I've got one open via #816 https://github.com/boxen/our-boxen/pull/816 however I before merging I was interested in the reasoning behind why using root has all of a sudden broke.
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/boxen/our-boxen/issues/814#issuecomment-205569490
https://github.com/boxen/puppet-homebrew/releases/tag/2.0.2 works for me, thanks!
It seems I'm unable to get this to work.
The error I'm getting when running script/boxen
is:
Error: Execution of 'brew update' returned 1: Error: Running Homebrew as root is extremely dangerous. As Homebrew does not
drop privileges on installation you are giving all build scripts full access
to your system. As a result of the macOS sandbox not handling the root user
correctly HOMEBREW_NO_SANDBOX has been set so the sandbox will not be used. If
we have not merged a pull request to add privilege dropping by November 1st
2016 running Homebrew as root will be disabled. No Homebrew maintainers plan
to work on this functionality.
Error: Cowardly refusing to 'sudo brew update'
You can use brew with sudo, but only if the brew executable is owned by root.
However, this is both not recommended and completely unsupported so do so at
your own risk.
Error: /Stage[main]/Homebrew::Repo/Homebrew_repo[/opt/boxen/homebrew]/min_revision: change from 7ac90613fd5a9719a03e180947522bfd4a8790be to e07584e3fbdc88327bafe23b9c40c904d0fff0a1 failed: Execution of 'brew update' returned 1: Error: Running Homebrew as root is extremely dangerous. As Homebrew does not
drop privileges on installation you are giving all build scripts full access
to your system. As a result of the macOS sandbox not handling the root user
correctly HOMEBREW_NO_SANDBOX has been set so the sandbox will not be used. If
we have not merged a pull request to add privilege dropping by November 1st
2016 running Homebrew as root will be disabled. No Homebrew maintainers plan
to work on this functionality.
Error: Cowardly refusing to 'sudo brew update'
You can use brew with sudo, but only if the brew executable is owned by root.
However, this is both not recommended and completely unsupported so do so at
your own risk.
I do have the newest boxen-homebrew
and have run bundle exec librarian-puppet install --path=shared --clean
:
github "homebrew", "2.0.2"
What could be the problem? Is there some cache I need to bust?
After upgrading homebrew to the latest version (apparently over the past weekend the maintainers split it into Homebrew/brew and Homebrew/homebrew-core?), I now get the following Puppet error when running
boxen
:Looks like something has changed upstream? attn @jacobbednarz who seems to be working on something related