Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot install alongside pyside6 on macOS ARM #269

Closed
hoechenberger opened this issue Dec 14, 2022 · 1 comment
Closed

Cannot install alongside pyside6 on macOS ARM #269

hoechenberger opened this issue Dec 14, 2022 · 1 comment
Labels

Comments

@hoechenberger
Copy link
Member

hoechenberger commented Dec 14, 2022

Comment:

When trying to install VTK 9.2 together with PySide6 on my ARM machine, I get an unresolvable dependency:

❯ mamba create -n test pyside6=6.4.1 vtk=9.2
[...]
Encountered problems while solving:
  - package pyside6-6.4.1-py310h6bbb1e2_0 requires libclang >=13.0.1,<14.0a0, but none of the providers can be installed

Trying with conda instead of mamba gives:

❯ conda create -n test pyside6=6.4.1 vtk=9.2
Collecting package metadata (current_repodata.json): done
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: -
Found conflicts! Looking for incompatible packages.
This can take several minutes.  Press CTRL-C to abort.
failed

UnsatisfiableError: The following specifications were found to be incompatible with each other:

Output in format: Requested package -> Available versions

Package sqlite conflicts for:
vtk=9.2 -> sqlite
vtk=9.2 -> proj[version='>=9.1.0,<9.1.1.0a0'] -> sqlite[version='>=3.33.0,<4.0a0|>=3.34.0,<4.0a0|>=3.35.5,<4.0a0|>=3.36.0,<4.0a0|>=3.37.0,<4.0a0|>=3.37.1,<4.0a0|>=3.38.5,<4.0a0|>=3.39.3,<4.0a0|>=3.39.0,<4.0a0']

Package jpeg conflicts for:
vtk=9.2 -> libnetcdf[version='>=4.8.1,<4.8.2.0a0'] -> jpeg[version='>=9d,<10a']
vtk=9.2 -> jpeg[version='>=9e,<10a']

Package libcxx conflicts for:
vtk=9.2 -> double-conversion[version='>=3.2.0,<3.3.0a0'] -> libcxx[version='>=11.0.0.rc1|>=11.0.0|>=11.1.0|>=14.0.6|>=13.0.1|>=12.0.1|>=11.0.1']
vtk=9.2 -> libcxx[version='>=14.0.4']

Package python conflicts for:
vtk=9.2 -> loguru -> python[version='3.10.*|3.11.*|>=3.5|>=3.6|3.8.*|3.9.*']
vtk=9.2 -> python[version='>=3.10,<3.11.0a0|>=3.10,<3.11.0a0|>=3.11,<3.12.0a0|>=3.8,<3.9.0a0|>=3.8,<3.9.0a0|>=3.9,<3.10.0a0|>=3.9,<3.10.0a0',build=*_cpython]

Package zlib conflicts for:
vtk=9.2 -> gl2ps[version='>=1.4.2,<1.4.3.0a0'] -> zlib[version='1.2.*|>=1.2.11,<1.3.0a0|>=1.2.12,<1.3.0a0']
vtk=9.2 -> zlib

Package libzlib conflicts for:
vtk=9.2 -> libnetcdf[version='>=4.8.1,<4.8.2.0a0'] -> libzlib[version='1.2.11|1.2.11|1.2.11|1.2.12|1.2.12|1.2.12|1.2.12|1.2.12|1.2.13|>=1.2.11,<1.3.0a0',build='hee7b306_1012|h90dfc92_1014|ha287fd2_1|h03a7124_4|h03a7124_3|ha287fd2_2|h90dfc92_0|hee7b306_1013']
vtk=9.2 -> libzlib[version='>=1.2.12,<1.3.0a0|>=1.2.13,<1.3.0a0']

Package tk conflicts for:
vtk=9.2 -> tk[version='>=8.6.12,<8.7.0a0']
vtk=9.2 -> python[version='>=3.10,<3.11.0a0'] -> tk[version='>=8.6.10,<8.7.0a0|>=8.6.11,<8.7.0a0']

Package libpng conflicts for:
vtk=9.2 -> libpng[version='>=1.6.38,<1.7.0a0']
vtk=9.2 -> freetype[version='>=2.12.1,<3.0a0'] -> libpng[version='>=1.6.23,<1.7|>=1.6.37,<1.7.0a0|>=1.6.39,<1.7.0a0']

Package libxml2 conflicts for:
vtk=9.2 -> libxml2[version='>=2.10.3,<2.11.0a0|>=2.9.14,<2.10.0a0|>=2.9.14,<2.11.0a0']
pyside6=6.4.1 -> libxslt[version='>=1.1.35,<2.0a0'] -> libxml2[version='>=2.10.3,<2.11.0a0|>=2.9.14,<2.11.0a0']
pyside6=6.4.1 -> libxml2[version='>=2.9.14,<2.10.0a0']

Package libsqlite conflicts for:
vtk=9.2 -> libsqlite[version='>=3.39.4,<4.0a0']
vtk=9.2 -> proj[version='>=9.1.0,<9.1.1.0a0'] -> libsqlite[version='3.39.2|3.39.3|3.39.4|3.40.0|>=3.39.3,<4.0a0|>=3.40.0,<4.0a0|>=3.39.2,<4.0a0',build='h2c9beb0_1|h76d750c_0']
Note that strict channel priority may have removed packages required for satisfiability.

The dependencies can be successfully resolved when requesting VTK 9.1 instead of 9.2, but I need 9.2 for my work.

I'm not sure if this is the right place to report this, or if it should be reported to the pyside6 feedstock maintainers instead?

In any case, thanks for any help and suggestions!

Richard

@hoechenberger
Copy link
Member Author

This has been resolved now, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant