How can I reproduce the symlinked home issue?

[osalbahr]

Output of brew config

HOMEBREW_VERSION: 4.6.8
ORIGIN: https://github.com/Homebrew/brew
HEAD: 9da27e1ac280ce720dfcbe6d5dac0dab2dcfc508
Last commit: 32 hours ago
Branch: HEAD
Core tap HEAD: 1960078a52058e175634f35e4733e87c276326e9
Core tap last commit: 27 hours ago
Core tap JSON: 03 Sep 16:24 UTC
HOMEBREW_PREFIX: /home/linuxbrew/.linuxbrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_FORBID_PACKAGES_FROM_PATHS: set
HOMEBREW_MAKE_JOBS: 4
Homebrew Ruby: 3.4.5 => /var/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/3.4.5/bin/ruby
CPU: quad-core 64-bit arm
Clang: N/A
Git: 2.34.1 => /bin/git
Curl: 7.81.0 => /bin/curl
Kernel: Linux 6.15.6-200.fc42.aarch64 aarch64 GNU/Linux
OS: Ubuntu 22.04.5 LTS
Host glibc: 2.35
/usr/bin/gcc: 11.4.0
/usr/bin/ruby: N/A
glibc: N/A
gcc@11: N/A
gcc: N/A
xorg: N/A

Output of brew doctor

Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Your /home directory is a symlink.
This is known to cause issues with formula linking, particularly when installing
multiple formulae that create symlinks in shared directories.

While this may be a standard directory structure in some distributions
(e.g. Fedora Silverblue) there are known issues as-is.

If you encounter linking issues, you may need to manually create conflicting
directories or use `brew link --overwrite` as a workaround.

We'd welcome a PR to fix this functionality.
See https://github.com/Homebrew/brew/issues/18036 for more context.

This is a Tier 2 configuration:
  https://docs.brew.sh/Support-Tiers#tier-2
You can report Tier 2 unrelated issues to Homebrew/* repositories!
Read the above document instead before opening any issues or PRs.


Warning: You have an unnecessary local Core tap!
This can cause problems installing up-to-date formulae.
Please remove it by running:
 brew untap homebrew/core

Warning: Your CPU architecture (arm64) is not supported. We only support
x86_64 CPU architectures. You will be unable to use binary packages (bottles).

This is a Tier 2 configuration:
  https://docs.brew.sh/Support-Tiers#tier-2
You can report Tier 2 unrelated issues to Homebrew/* repositories!
Read the above document instead before opening any issues or PRs.

Description of issue

I would like to reproduce the following issue:

• Brew link step fail if installing multiple formulae with common symlink using a system with symlinked /home brew#18036

But running brew install docker-buildx gives me the following:

Warning: Your CPU architecture (arm64) is not supported. We only support
x86_64 CPU architectures. You will be unable to use binary packages (bottles).

This is a Tier 2 configuration:
  https://docs.brew.sh/Support-Tiers#tier-2
You can report Tier 2 unrelated issues to Homebrew/* repositories!
Read the above document instead before opening any issues or PRs.

==> Fetching downloads for: docker-buildx
Error: docker-buildx: no bottle available!
If you're feeling brave, you can try to install from source with:
  brew install --build-from-source docker-buildx

This is a Tier 3 configuration:
  https://docs.brew.sh/Support-Tiers#tier-3
Do not report any issues to Homebrew/* repositories!
Read the above document instead before opening any issues or PRs.
==> No outdated dependents to upgrade!

Are there other formulas I can use to reproduce the issue while still using bottles?

---

Note: I am using the homebrew/ubuntu22.04 container and ran the following to simulate the Fedora Silverblue (symlinked /home) environment:

$ cd /
$ sudo mv home var
$ sudo ln -s var/home .

[osalbahr]

I also tried to replicate the following:

• brew install mesa fails at link step on Fedora Silverblue (probably not a formula bug) brew#16943

But installing mesa seems to just work.

[SMillerDev]

I think you'll need to reproduce it in fedora, I don't think the actual symlink is the biggest difference there.

[osalbahr]

Thank you for the suggestion. I just installed Homebrew on Fedora Silverblue 42 (latest) in a UTM VM and I was able to brew install mesa.