(release/0.5) ./install_requirements.sh fails due to conflicting dependencies.

[cobernhart]

🐛 Describe the bug

I am on a Mac M2 machine and have followed exactly this tutorial for setup:
https://pytorch.org/executorch/stable/getting-started-setup.html#quick-setup-colab-jupyter-notebook-prototype

When running the ./install_requirements.sh script it starts installing until I receive following error

ERROR: Cannot install timm==1.0.7, torch==2.6.0, torchaudio==2.6.0 and torchvision==0.21.0 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested torch==2.6.0
    torchvision 0.21.0 depends on torch==2.6.0
    timm 1.0.7 depends on torch
    torchaudio 2.6.0 depends on torch==2.7.0

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip to attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

Versions

PyTorch version: N/A
Is debug build: N/A
CUDA used to build PyTorch: N/A
ROCM used to build PyTorch: N/A

OS: macOS 15.3.2 (arm64)
GCC version: Could not collect
Clang version: 16.0.0 (clang-1600.0.26.6)
CMake version: version 3.31.6
Libc version: N/A

Python version: 3.10.0 (default, Mar 3 2022, 03:54:28) [Clang 12.0.0 ] (64-bit runtime)
Python platform: macOS-15.3.2-arm64-arm-64bit
Is CUDA available: N/A
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: N/A

CPU:
Apple M2

Versions of relevant libraries:
[pip3] numpy==1.21.3
[conda] numpy 1.21.3 pypi_0 pypi

cc @larryliu0820 @jathu @lucylq

[kimishpatel]

@larryliu0820 @Jack-Khuu who among you is the right person to answer this?

[dreamqin68]

I encountered the same error when using the latest release v0.5.0.

[kimishpatel]

cc: @JacobSzwejbka

[jhelsby]

I encountered the same error today using the latest release, v0.5.0a0. On an M1 MacBook Pro.

Edit: I don't think this is directly relevant, but adding for completeness. I was able to successfully build on the same M1 MacBook Pro, inside a Linux Fedora VM in VMWare Fusion.

[margaritaG]

I encountered the same issue this morning.

My workaround was to switch to the main branch (instead of release/0.5), and then follow the steps in here.

The main branch is less stable than the latest release, but it's better than nothing while waiting for this issue to be fixed on release branch.