Open stefansundin opened 7 months ago
Or maybe check that the empty directories do not belong to bare git repository?
This seems reasonable.
That said: we should probably configure our Rubies/Bundlers to set BUNDLE_PATH: "vendor/ruby"
and maybe BUNDLE_DISABLE_SHARED_GEMS: "true"
by default. Installing to the Homebrew prefix should be avoided for reasons exactly like this.
Yep, this is a known issue seen in our own projects too. Thanks for filing an issue on this to track.
brew doctor
outputVerification
brew doctor
output" above saysYour system is ready to brew.
and am still able to reproduce my issue.brew update
twice and am still able to reproduce my issue.brew install wget
. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.brew config
outputWhat were you trying to do (and why)?
I have a ruby project with a Gemfile that sources a gem from a git source. When I run
bundle update
to check for gem updates, this particular gem has been having issues, seemingly randomly. Today I figured out that this issue happens afterbrew cleanup
has been run.What happened (include all command output)?
At this point, everything is working just fine. Here's how to break it:
The fix is to manually delete the directory at
/opt/homebrew/lib/ruby/gems/3.3.0/cache/bundler/git/clogger-b0c912e9759a20a9c2aa868294b5d44dfbaf537f
and then runbundle update
again.I don't know the best fix for this problem, but maybe
brew cleanup
shouldn't mess with the ruby gems directory at all? Or maybe check that the empty directories do not belong to bare git repository?What did you expect to happen?
I expect
brew cleanup
to not breakbundle update
.Step-by-step reproduction instructions (by running
brew
commands)