red11
February 15, 2025, 9:14am
1
Brew was working fine yesterday on my Blufin. Yesterday I have poweroff laptop and today I have turned it on. Executing command: brew
I get: “bash: brew: command not found”.
which brew
returns: “/usr/bin/which: no brew in (/var/home/user1/.local/bin:/var/home/user1/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin)”
It looks like brew got somehow corrupted on my Blufin. Any idea how to get it back?
rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: last run 2min 4s ago
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:stable
Digest: sha256:308f2addc0874bb901680a8bf8b8a817cf9e102ac3e6d40dac7a0955f42ad1df
Version: 41.20250209.1 (2025-02-09T06:02:01Z)
Pinned: yes
JohnAtl
February 15, 2025, 10:04am
2
There is someone else with the problem too.
Hello,
I thought bluefin would come with homebrew installed. However I get the error message:
pbeccard@rubicon:~$ brew
bash: brew: Kommando nicht gefunden.
Am I doing something wrong?
pbeccard@rubicon:~$ cat /etc/os-release
NAME="Bluefin"
VERSION="41.20250209.1 (Silverblue)"
RELEASE_TYPE=stable
ID=bluefin
ID_LIKE="fedora"
VERSION_ID=41
VERSION_CODENAME="Archaeopteryx"
PLATFORM_ID="platform:f41"
PRETTY_NAME="Bluefin (Version: 41.20250209.1 / FROM Fedora Silverblue 41)"
ANSI_COLOR="0;38;2;60;…
It seems that brew just… didnt get evaluated for some reason??
Do you mind running eval /etc/profile.d/brew.sh
and seeing if brew shows up on your PATH again? It should be properly installed, dunno what exactly is going on here
red11
February 16, 2025, 9:44am
4
I executed above command and brew
command still displays “command not found”.
red11
February 21, 2025, 1:59pm
5
I have now fixed the problem. I haven’t had anything super important installed in brew, so I could afford to do some “magic”.
Move to brew directory.
cd /var/home/linuxbrew
Removed everything in this directory (DANGER: You can lose everything related to brew)
rm -rf *
Install brew with script:
. /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
Close the terminal and open new terminal.
Check if brew is working fine.
brew doctor
and it displays “Your system is ready to brew.”
Install vifm terminal file manager application
brew install vifm
and application is installed successfully.
Start a program
vifm
and application starts successfully.
Problem solved.
thanks, this got it working again for me.
since found an easier way to do this :
opened 01:26AM - 24 Jan 25 UTC
brew
### Describe the bug
All `brew` commands, besides `brew info`, fail.
### What … did you expect to happen?
I expected `brew` to work properly, as per usual.
### Output of `bootc status`
```shell
No staged image present
Current booted image: ghcr.io/ublue-os/bluefin-dx:stable
Image version: 41.20250119.1 (2025-01-19 06:04:01 UTC)
Image digest: sha256:2d97f2b0fe268f63604f12300fddca3324c76c207968b1416b9984783bbe83fa
Current rollback image: ghcr.io/ublue-os/bluefin-dx:stable
Image version: 41.20250114 (2025-01-14 03:47:26 UTC)
Image digest: sha256:964f63000d7bbedb53362399a596b4df41d59d7a7cbdd1d699ed8e06d5c62305
```
### Output of `groups`
```shell
raindrop wheel
```
### Extra information or context
Different commands seem to be outputting slightly different errors. Most commands output the following:
```
❯ brew info
<internal:/var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/3.3.6/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require': cannot load such file -- sorbet-runtime (LoadError)
from <internal:/var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/3.3.6/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
from /var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/standalone/sorbet.rb:4:in `<top (required)>'
from /var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/startup.rb:10:in `require_relative'
from /var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/startup.rb:10:in `<top (required)>'
from /var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/global.rb:4:in `require_relative'
from /var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/global.rb:4:in `<top (required)>'
from /var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/brew.rb:18:in `require_relative'
from /var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/brew.rb:18:in `<main>'
```
While some other commands output the following error instead:
```
❯ brew install
/var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/brew.sh: line 1010: homebrew-update: command not found
<internal:/var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/3.3.6/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require': cannot load such file -- sorbet-runtime (LoadError)
from <internal:/var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/3.3.6/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
from /var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/standalone/sorbet.rb:4:in `<top (required)>'
from /var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/startup.rb:10:in `require_relative'
from /var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/startup.rb:10:in `<top (required)>'
from /var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/global.rb:4:in `require_relative'
from /var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/global.rb:4:in `<top (required)>'
from /var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/brew.rb:18:in `require_relative'
from /var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/brew.rb:18:in `<main>'
```
Mshrm
February 27, 2025, 2:04am
7
I have the same issue recently too. I will try one of these solutions and report back.
Mshrm
February 27, 2025, 1:34pm
8
I tried this but when I open a new terminal and run brew doctor
I get bash: brew: command not found
. The script did run so I don’t know why this isn’t working. Any suggestions?
Mshrm
February 27, 2025, 1:56pm
9
I followed the instructions at the end of the install script after the install completed and now it is working.