Open asen23 opened 2 months ago
@asen23 Thanks for the issue!
@Homebrew/maintainers given we have a few known issues with symlinked homes that no maintainers seem to be running into or personally working on fixing: I'm increasing tempted to say we should have a brew doctor
warning for it. Thoughts?
Sounds ok to me. There's a relatively straightforward workaround for this particular issue: https://github.com/Homebrew/homebrew-core/issues/181016#issuecomment-2285619753
Related issues can be handled in the same way.
The issue is that a symlinked /home
confuses brew
into mishandling the way it resolves symlinked directories, and the workaround is for the user to resolve the conflict themselves by manually creating the directory.
@Homebrew/maintainers given we have a few known issues with symlinked homes that no maintainers seem to be running into or personally working on fixing: I'm increasing tempted to say we should have a
brew doctor
warning for it. Thoughts?
I don't mind if workaround is available, also if it possible to put the message in the brew link error it could give more visibility
Sounds ok to me. There's a relatively straightforward workaround for this particular issue: Homebrew/homebrew-core#181016 (comment)
Yeh, the workaround here and how we're saying "PRs, not issues" communicates brew doctor
to me at a minimum, if not even a warning on all installations.
In current state of Homebrew, Fedora Silverblue and similar systems should probably fall into the "unsupported" category like ARM Linux and old macOS versions. It seems reasonable to add message to brew doctor
and maybe additional info at https://docs.brew.sh/Homebrew-on-Linux
@cho-m Strongly agreed.
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)?
Installing docker-compose and docker-buildx in my machine.
What happened (include all command output)?
the first one to be installed will be installed correctly but the second one to be installed will fail the
brew link
step logsWhat did you expect to happen?
Both are installed and usable without conflict.
Step-by-step reproduction instructions (by running
brew
commands)