Closed Delengowski closed 1 year ago
Hi! This is a known incompatibility with recent versions of conda
. We have a patch ready for the next release (coming soon), but for now what you can do is to have a new environment with constructor
and an older conda
, à la:
$ conda create -n constructor-workaround python=3.9 constructor conda=22.11
And then run constructor from that env. Hope that works!
@jaimergp Does conda=22.11
have libmamba compatibility? I believe that's why I upgraded. I built the environment with libmamba
but when I was using constructor
with an older version that couldn't use the experimental solver, it was finding inconsistencies.
It should be compatible, yes. Just make sure to have conda-libmamba-solver
in that new env too.
@jaimergp when is the new release going to happen?
With this older conda I get these connection issues that cannot get through my proxies
Traceback (most recent call last):
File "/home/delengowski/miniconda3/envs/constructor-workaround/bin/constructor", line 10, in <module>
sys.exit(main())
File "/home/delengowski/miniconda3/envs/constructor-workaround/lib/python3.9/site-packages/constructor/main.py", line 351, in main
main_build(dir_path, output_dir=out_dir, platform=args.platform,
File "/home/delengowski/miniconda3/envs/constructor-workaround/lib/python3.9/site-packages/constructor/main.py", line 149, in main_build
fcp_main(info, verbose=verbose, dry_run=dry_run, conda_exe=conda_exe)
File "/home/delengowski/miniconda3/envs/constructor-workaround/lib/python3.9/site-packages/constructor/fcp.py", line 497, in main
) = _main(
File "/home/delengowski/miniconda3/envs/constructor-workaround/lib/python3.9/site-packages/constructor/fcp.py", line 384, in _main
precs = _solve_precs(
File "/home/delengowski/miniconda3/envs/constructor-workaround/lib/python3.9/site-packages/constructor/fcp.py", line 315, in _solve_precs
precs = list(solver.solve_final_state())
File "/home/delengowski/miniconda3/envs/constructor-workaround/lib/python3.9/site-packages/conda_libmamba_solver/solver.py", line 167, in solve_final_state
index = LibMambaIndexHelper(
File "/home/delengowski/miniconda3/envs/constructor-workaround/lib/python3.9/site-packages/conda_libmamba_solver/index.py", line 71, in __init__
self._index = self._load_channels()
File "/home/delengowski/miniconda3/envs/constructor-workaround/lib/python3.9/site-packages/conda_libmamba_solver/index.py", line 246, in _load_channels
full_index += get_index_libmamba(
File "/home/delengowski/miniconda3/envs/constructor-workaround/lib/python3.9/site-packages/conda_libmamba_solver/mamba_utils.py", line 102, in get_index
is_downloaded = dlist.download(api.MAMBA_DOWNLOAD_FAILFAST)
RuntimeError: Download error (6) Couldn't resolve host name [https://conda.anaconda.org/conda-forge/noarch/repodata.json]
Could not resolve host: conda.anaconda.org
@jaimergp when is the new release going to happen?
Next week I hope! You can also try to install from main
via pip install https://github.com/conda/constructor/archive/main.tar.gz --no-deps
in fully upgraded environment (recent conda and so on). The point is to override the conda-provided constructor with the pip provided one.
Pip install did it, thank you!
Checklist
What happened?
I run
constructor .
to try to build an installer and I receive the following trace backI researched the error and found this related topic under anaconda-issues so I deleted the associated cache dir but the problem still exists.
Conda Info
Conda Config
Conda list
Additional Context
Full output from command
constructor .
The associated
construct.yaml
fileI try to debug the command, in hopes of determining the problematic package and I receive a different error.
python -m pdb $(which constructor) .