audio: Are the nightly conda builds broken?
13:35 $ conda install pytorch torchvision torchaudio -c pytorch-nightly
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
PackagesNotFoundError: The following packages are not available from current channels:
- torchaudio
Current channels:
- https://conda.anaconda.org/pytorch-nightly/osx-arm64
- https://conda.anaconda.org/pytorch-nightly/noarch
- https://repo.anaconda.com/pkgs/main/osx-arm64
- https://repo.anaconda.com/pkgs/main/noarch
- https://repo.anaconda.com/pkgs/r/osx-arm64
- https://repo.anaconda.com/pkgs/r/noarch
To search for alternate channels that may provide the conda package you're
looking for, navigate to
https://anaconda.org
and use the search bar at the top of the page.
Tested just now on OSX
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 22 (6 by maintainers)
Commits related to this issue
- Recent CircleCI migration #2529 silently bumped the minimum supported macOS version to 11. PyTorch still supports 10.9 and the ecosystem still uses 10.9. Issue: #2536 This commit sets MACOSX_DEPLOYM... — committed to mthrok/audio by mthrok 2 years ago
- Set MACOSX_DEPLOYMENT_TARGET=10.9 in binary build jobs (#2546) Summary: Recent CircleCI migration https://github.com/pytorch/audio/pull/2529 silently bumped the minimum supported macOS version to 11.... — committed to pytorch/audio by mthrok 2 years ago
- Set MACOSX_DEPLOYMENT_TARGET=10.9 in binary build jobs (#2546) Summary: Recent CircleCI migration https://github.com/pytorch/audio/pull/2529 silently bumped the minimum supported macOS version to 11.... — committed to pytorch/audio by mthrok 2 years ago
Hmm, I see the same problem. Looks like something have change in the ecosystem:
conda install pytorch -c pytorch
attempts to install pytorch-1.10.2 rather than 1.11@malfet I also get this issue with the main pytorch channel too. It was working fine a couple days ago. Using M1 macOS 12.4 / arm miniconda. Was there any change with the main pytorch channel ?