Conda install of master fails for me.

[Wayne Gramlich]

Greetings:

First post here.

I saw the Hack-a-Day article in early February and I have mostly switched my code from struggling to do things using the FreeCAD Python interface to the CadQuery one.  I want to thank people for doing CadQuery.

I'm getting ready to share my code with a friend and I generally like to write down the installation instructions and test them in a clean Linux environment (Ubuntu 20.04LTS) running under VirtualBox. I have no problems installing Cadquery 2.1 in MiniForge, MiniConda, and Andconda, but the master branch fails in all three.  MiniForge and MiniCon fail without any diagnostics, but Anaconda does provide some information. The install is shown below:

(cadquery-dev) wayne@wayne-VirtualBox:  conda install -c cadquery -c conda-forge cadquery=master

Collecting package metadata (current_repodata.json): done
Solving environment: -
The environment is inconsistent, please check the package plan carefully
The following packages are causing the inconsistency:

  - conda-forge/noarch::charset-normalizer==2.0.12=pyhd8ed1ab_0
  - conda-forge/linux-64::python_abi==3.9=2_cp39
  - conda-forge/linux-64::conda==4.11.0=py39hf3d152e_0
  - conda-forge/linux-64::cryptography==36.0.1=py39h95dcef6_0
  - conda-forge/noarch::wheel==0.37.1=pyhd8ed1ab_0
  - conda-forge/noarch::urllib3==1.26.8=pyhd8ed1ab_1
  - conda-forge/linux-64::ruamel_yaml==0.15.80=py39h3811e60_1006
  - conda-forge/linux-64::conda-package-handling==1.7.3=py39h3811e60_1
  - conda-forge/linux-64::brotlipy==0.7.0=py39h3811e60_1003
  - conda-forge/linux-64::setuptools==60.9.3=py39hf3d152e_0
  - conda-forge/linux-64::python==3.9.10=h85951f9_2_cpython
  - conda-forge/noarch::requests==2.27.1=pyhd8ed1ab_0
  - conda-forge/noarch::pycparser==2.21=pyhd8ed1ab_0
  - conda-forge/noarch::tqdm==4.62.3=pyhd8ed1ab_0
  - conda-forge/noarch::pyopenssl==22.0.0=pyhd8ed1ab_0
  - conda-forge/noarch::six==1.16.0=pyh6c4a22f_0
  - conda-forge/linux-64::cffi==1.15.0=py39h4bc2ebd_0
  - conda-forge/noarch::pip==22.0.3=pyhd8ed1ab_0
  - conda-forge/noarch::idna==3.3=pyhd8ed1ab_0
  - conda-forge/noarch::colorama==0.4.4=pyh9f0ad1d_0
  - conda-forge/linux-64::sqlite==3.37.0=h9cd32fc_0
  - conda-forge/linux-64::certifi==2021.10.8=py39hf3d152e_1
  - conda-forge/linux-64::pycosat==0.6.3=py39h3811e60_1009
  - conda-forge/linux-64::pysocks==1.7.1=py39hf3d152e_4
failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): \

This feels like some sort of Python 3.8 vs. Python 3.9 version issue, but I'm not sure.  (Anaconda is a black box to me.) This is not currently a blocker for me, but I'm wondering if other people are having this problem.  Any insight would be greatly appreciated.

Regards,

-Wayne

[Lorenz Neureuter]

Hi Wayne,

How much memory did you allocate to the VM?  The conda installation may have failed due to out of memory.

You might try allocating more memory or try mamba which I have found to use less memory.

Lorenz

--
cadquery home: https://github.com/CadQuery/cadquery
post issues at https://github.com/CadQuery/cadquery/issues
run it at home at : https://github.com/CadQuery/CQ-editor
---
You received this message because you are subscribed to the Google Groups "CadQuery" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cadquery+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cadquery/d0cc9806-d6c2-45c1-aeed-5460a103d3d7n%40googlegroups.com.

[Jeremy Wright]

There are also pre-built development packages of CQ-editor that might be easier for your friend to use.

To view this discussion on the web visit https://groups.google.com/d/msgid/cadquery/CAGfJF%3D3HGm_QKGn%2BNeGNjy0b9ytM%3DHveMBocESkHy9OKM1wHkw%40mail.gmail.com.

[Wayne Gramlich]

All:

Thanks for your prompt responses.  It turns out for me, it was both a Virtual Memory and Disk Usage issue on virtual machine.  I just used the defaults for memory/disk (2GB and 10GB respectively.)  It is easy to increase the virtual memory, but a bit harder to resize and extend and disk drive for a VirtualBox virtual machine.  So, I threw my virtual machine image away, started a new roomier one, which took a while.  When I looked at the disk utilization afterwards, the disk usage was up to 15GB.

Everything is installed and working now.  Thanks, it would have taken me a while to figure this all out.

-Wayne