Closed timj closed 1 year ago
ocefpaf
commented
1 year ago I don't have a mac to test but I was able to create a dry-run env with:
CONDA_SUBDIR=osx-64 conda env create --name TEST "python=3.10" "depfinder>=2.10.0" --dry-runCan you test conda env create --name TEST "python=3.10" "depfinder>=2.10.0" there?
timj
commented
1 year ago $ conda env create --name TEST "python=3.10" "depfinder>=2.10.0"
usage: conda-env [-h] {create,export,list,remove,update,config} ...
conda-env: error: unrecognized arguments: depfinder>=2.10.0No idea why that doesn't work. If osx-64 is working for you then maybe this is entirely an osx-arm64 problem.
ocefpaf
commented
1 year ago That may be the fact that my "conda" is actually micromamba. Can you try to create and empty env with Python 3.10 and then install depfinder>=2.10.0? It is noarch so it should be osx-arm64 ready.
timj
commented
1 year ago It tries to install the broken 2.7.1:
$ conda create -n TEST python=3.10
Collecting package metadata (current_repodata.json): done
Solving environment: done
## Package Plan ##
environment location: /Users/timj/work/lsstsw/miniconda/envs/TEST
added / updated specs:
- python=3.10
The following NEW packages will be INSTALLED:
bzip2 conda-forge/osx-arm64::bzip2-1.0.8-h3422bc3_4
ca-certificates conda-forge/osx-arm64::ca-certificates-2023.5.7-hf0a4a13_0
libffi conda-forge/osx-arm64::libffi-3.4.2-h3422bc3_5
libsqlite conda-forge/osx-arm64::libsqlite-3.42.0-hb31c410_0
libzlib conda-forge/osx-arm64::libzlib-1.2.13-h03a7124_4
ncurses conda-forge/osx-arm64::ncurses-6.3-h07bb92c_1
openssl conda-forge/osx-arm64::openssl-3.1.1-h53f4e23_1
pip conda-forge/noarch::pip-23.1.2-pyhd8ed1ab_0
python conda-forge/osx-arm64::python-3.10.11-h3ba56d0_0_cpython
readline conda-forge/osx-arm64::readline-8.2-h92ec313_1
setuptools conda-forge/noarch::setuptools-67.7.2-pyhd8ed1ab_0
tk conda-forge/osx-arm64::tk-8.6.12-he1e0b03_0
tzdata conda-forge/noarch::tzdata-2023c-h71feb2d_0
wheel conda-forge/noarch::wheel-0.40.0-pyhd8ed1ab_0
xz conda-forge/osx-arm64::xz-5.2.6-h57fd34a_0
Proceed ([y]/n)? y
Downloading and Extracting Packages
Preparing transaction: done
Verifying transaction: done
Executing transaction: done
#
# To activate this environment, use
#
# $ conda activate TEST
#
# To deactivate an active environment, use
#
# $ conda deactivate
(base) stargazer:timj $ conda activate TEST
(TEST) stargazer:timj $ conda install depfinder
Collecting package metadata (current_repodata.json): done
Solving environment: unsuccessful initial attempt using frozen solve. Retrying with flexible solve.
Solving environment: unsuccessful attempt using repodata from current_repodata.json, retrying with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: done
## Package Plan ##
environment location: /Users/timj/work/lsstsw/miniconda/envs/TEST
added / updated specs:
- depfinder
The following packages will be downloaded:
package | build
---------------------------|-----------------
python_abi-3.10 | 3_cp310 6 KB conda-forge
------------------------------------------------------------
Total: 6 KB
The following NEW packages will be INSTALLED:
depfinder conda-forge/noarch::depfinder-2.7.1-pyhd8ed1ab_1
python_abi conda-forge/osx-arm64::python_abi-3.10-3_cp310
pyyaml conda-forge/osx-arm64::pyyaml-6.0-py310h8e9501a_5
stdlib-list conda-forge/noarch::stdlib-list-0.8.0-pyhd8ed1ab_0
yaml conda-forge/osx-arm64::yaml-0.2.5-h3422bc3_2
Proceed ([y]/n)? I get the same behavior with python 3.11.
timj
commented
1 year ago Okay, turns out that the conda-forge page is telling us exactly the problem: https://anaconda.org/conda-forge/depfinder
noarch is only for v2.8.1.
ocefpaf
commented
1 year ago That's why I asked you to request "depfinder>=2.10.0" instead of just depfinder, to force that version.
timj
commented
1 year ago Yes, but it can't find something if conda search can't find it.
$ conda install "depfinder>=2.10"
Collecting package metadata (current_repodata.json): done
Solving environment: unsuccessful initial attempt using frozen solve. Retrying with flexible solve.
Collecting package metadata (repodata.json): done
Solving environment: unsuccessful initial attempt using frozen solve. Retrying with flexible solve.
PackagesNotFoundError: The following packages are not available from current channels:
- depfinder[version='>=2.10']
Current channels:
- https://conda.anaconda.org/conda-forge/osx-arm64
- https://conda.anaconda.org/conda-forge/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.$ conda search depfinder
Loading channels: done
# Name Version Build Channel
depfinder 2.1.1 py_1 conda-forge
depfinder 2.2.0 py_0 conda-forge
depfinder 2.2.1 py_0 conda-forge
depfinder 2.3.0 py_0 conda-forge
depfinder 2.3.1 py_0 conda-forge
depfinder 2.4.0 py_0 conda-forge
depfinder 2.4.1 py_0 conda-forge
depfinder 2.5.1 pyhd8ed1ab_0 conda-forge
depfinder 2.6.0 pyhd8ed1ab_0 conda-forge
depfinder 2.6.1 pyhd8ed1ab_0 conda-forge
depfinder 2.6.2 pyhd8ed1ab_0 conda-forge
depfinder 2.7.0 pyhd8ed1ab_0 conda-forge
depfinder 2.7.1 pyhd8ed1ab_0 conda-forge
depfinder 2.7.1 pyhd8ed1ab_1 conda-forge
depfinder 2.8.0 pyhd8ed1ab_0 conda-forge
depfinder 2.8.1 pyhd8ed1ab_0 conda-forge There is no arm mac build so it's falling back to the noarch one which is 2.8.1 as shown on the anaconda web page.
ocefpaf
commented
1 year ago I'm always confused about noarch on osx-arm64. We can try to add it to the migrator and see if that creates a variant for it.
timj
commented
1 year ago ocefpaf
commented
1 year ago Ideally we should issue a new depfinder version that is Python >=3.10 only and make it noarch again. But for now, https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/4530 should do the trick.
Solution to issue cannot be found in the documentation.
Issue
When I search for depfinder with python 3.10 macOS ARM I get:
If I install depfinder it gives me v2.7.1 which doesn't work:
v2.8.1 refuses to install because that one knows that stdlib-list does not work on python 3.10. It seems like a related issue is that stdlib-list is not pinned for <3.10.
v2.10 should work on python 3.10 because that uses
sys.stdlib_module_namesbut is not available to me. I don't know if that is macOS-specific or a general feedstock problem.Installed packages
Environment info