You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suppose this is kind of expected, since normally brew installs its own dependencies when running some development commands for the first time, but is not allowed to modify the nix store:
$ brew livecheck --debug kde-mac/kde/kdeconnectError: Permission denied @ rb_sysopen - /nix/store/v19ip7y08262kadi01g4wnrr8cxd9qbx-brew-4.3.5-patched/Library/Homebrew/vendor/bundle/ruby/3.3.0/.homebrew_vendor_versionWarning: Removed Sorbet lines from backtrace!Rerun with `--verbose` to see the original backtrace/nix/store/v19ip7y08262kadi01g4wnrr8cxd9qbx-brew-4.3.5-patched/Library/Homebrew/utils/gems.rb:296:in `write'/nix/store/v19ip7y08262kadi01g4wnrr8cxd9qbx-brew-4.3.5-patched/Library/Homebrew/utils/gems.rb:296:in `write'/nix/store/v19ip7y08262kadi01g4wnrr8cxd9qbx-brew-4.3.5-patched/Library/Homebrew/utils/gems.rb:296:in `install_bundler_gems!'/nix/store/v19ip7y08262kadi01g4wnrr8cxd9qbx-brew-4.3.5-patched/Library/Homebrew/dev-cmd/livecheck.rb:52:in `run'/opt/homebrew/Library/Homebrew/brew.rb:92:in `<main>'
Is there some workaround I can use to either
preinstall the necessary dependencies in the patched brew (maybe a new nix-homebrew.setupCommands or something that can run some commands to install gems?)
tell brew to install in some other location, or give it a mutable directory to install stuff to?
The text was updated successfully, but these errors were encountered:
I suppose this is kind of expected, since normally
brew
installs its own dependencies when running some development commands for the first time, but is not allowed to modify the nix store:Is there some workaround I can use to either
nix-homebrew.setupCommands
or something that can run some commands to install gems?)brew
to install in some other location, or give it a mutable directory to install stuff to?The text was updated successfully, but these errors were encountered: