Git Product home page Git Product logo

Comments (11)

traversaro avatar traversaro commented on September 13, 2024 3

The issue is intricate, but a workaround was added in #15 .

from ironcub-mk1-software.

traversaro avatar traversaro commented on September 13, 2024 2

This is similar to robotology/gazebo-yarp-plugins#660 and robotology/gazebo-yarp-plugins#664 . Indeed, for some reason ogre 1.10.12 hbcc8020_2 (that is quite old) get installed. How did you create the environment that you used? Can you create a new one?

from ironcub-mk1-software.

traversaro avatar traversaro commented on September 13, 2024 2

(BTW, this is a good advertisement for the need to commit a lock file to the repo, but that is another story).

Ok, I was able to reproduce the problem.

from ironcub-mk1-software.

traversaro avatar traversaro commented on September 13, 2024 2

So, to debug the problem I created two environments, one corresponding to the file

mamba create -n test123 -c conda-forge -c robotology gazebo gazebo-yarp-plugins pyyaml=5 git git-lfs compilers cmake pkg-config make ninja icub-models idyntree-matlab-bindings wb-toolbox whole-body-controllers whole-body-estimators opencv catkin_pkg

and one in which I asked explicitly for a modern ogre:

mamba create -n test124 -c conda-forge -c robotology gazebo gazebo-yarp-plugins pyyaml=5 git git-lfs compilers cmake pkg-config make ninja icub-models idyntree-matlab-bindings wb-toolbox whole-body-controllers whole-body-estimators opencv catkin_pkg ogre=1.10.12=*_15

I will then check the difference between the two lists, to understand what is the package that conflicting with a new ogre. The diff is:

--- <unnamed>
+++ <unnamed>
@@ -122,18 +122,18 @@
 libogg                    1.3.4                h8ffe710_1    conda-forge
 libopenblas               0.3.24          pthreads_hc140b1d_0    conda-forge
 libopencv                 4.8.1           py311h6be31c5_4    conda-forge
-libopenvino               2023.1.0             h63175ca_1    conda-forge
-libopenvino-auto-batch-plugin 2023.1.0             h63175ca_1    conda-forge
-libopenvino-auto-plugin   2023.1.0             h63175ca_1    conda-forge
-libopenvino-hetero-plugin 2023.1.0             h63175ca_1    conda-forge
-libopenvino-intel-cpu-plugin 2023.1.0             h63175ca_1    conda-forge
-libopenvino-intel-gpu-plugin 2023.1.0             h63175ca_1    conda-forge
-libopenvino-ir-frontend   2023.1.0             h63175ca_1    conda-forge
-libopenvino-onnx-frontend 2023.1.0             h63175ca_1    conda-forge
-libopenvino-paddle-frontend 2023.1.0             h63175ca_1    conda-forge
-libopenvino-pytorch-frontend 2023.1.0             h63175ca_1    conda-forge
-libopenvino-tensorflow-frontend 2023.1.0             h63175ca_1    conda-forge
-libopenvino-tensorflow-lite-frontend 2023.1.0             h63175ca_1    conda-forge
+libopenvino               2023.1.0             h63175ca_0    conda-forge
+libopenvino-auto-batch-plugin 2023.1.0             h63175ca_0    conda-forge
+libopenvino-auto-plugin   2023.1.0             h63175ca_0    conda-forge
+libopenvino-hetero-plugin 2023.1.0             h63175ca_0    conda-forge
+libopenvino-intel-cpu-plugin 2023.1.0             h63175ca_0    conda-forge
+libopenvino-intel-gpu-plugin 2023.1.0             h63175ca_0    conda-forge
+libopenvino-ir-frontend   2023.1.0             h63175ca_0    conda-forge
+libopenvino-onnx-frontend 2023.1.0             h63175ca_0    conda-forge
+libopenvino-paddle-frontend 2023.1.0             h63175ca_0    conda-forge
+libopenvino-pytorch-frontend 2023.1.0             h63175ca_0    conda-forge
+libopenvino-tensorflow-frontend 2023.1.0             h63175ca_0    conda-forge
+libopenvino-tensorflow-lite-frontend 2023.1.0             h63175ca_0    conda-forge
 libopus                   1.3.1                h8ffe710_1    conda-forge
 libosqp                   0.6.3                h63175ca_0    conda-forge
 libpng                    1.6.39               h19919ed_0    conda-forge
@@ -175,7 +175,7 @@
 ninja                     1.11.1               h91493d7_0    conda-forge
 numpy                     1.26.0          py311h0b4df5a_0    conda-forge
 octomap                   1.9.8                h91493d7_0    conda-forge
-ogre                      1.10.12              hbcc8020_2    conda-forge
+ogre                      1.10.12             ha04c5d8_15    conda-forge
 openal-soft               1.22.2               h2d74725_0    conda-forge
 openblas                  0.3.24          pthreads_h3721920_0    conda-forge
 opencv                    4.8.1           py311h25e42d1_4    conda-forge
@@ -197,7 +197,7 @@
 proj                      9.3.0                he13c7e8_2    conda-forge
 pthread-stubs             0.4               hcd874cb_1001    conda-forge
 pthreads-win32            2.9.1                hfa6e2cd_3    conda-forge
-pugixml                   1.14                 h63175ca_0    conda-forge
+pugixml                   1.13                 h63175ca_1    conda-forge
 py-opencv                 4.8.1           py311hd5bf162_4    conda-forge
 pybind11-abi              4                    hd8ed1ab_3    conda-forge
 pyparsing                 3.1.1              pyhd8ed1ab_0    conda-forge
@@ -263,3 +263,4 @@
 zeromq                    4.3.5                h63175ca_0    conda-forge
 zlib                      1.2.13               hcfcfb64_5    conda-forge
 zstd                      1.5.5                h12be248_0    conda-forge
+zziplib                   0.13.69              h1d00b33_1    conda-forge

So there is some conflict between the newest pugixml and the newest libopenvino, that is a dependency of libopencv.

from ironcub-mk1-software.

traversaro avatar traversaro commented on September 13, 2024 2

Ok, the problem is that one openvino plugin is linked to pugixml 1.14 even if the rest of the feedstocks are pinned/migrated to 1.13 :

C:\Users\straversaro>mamba create -n test125 libopenvino-dev=2023.1.0=*_1 ogre=1.10.12=*_15

Looking for: ['libopenvino-dev==2023.1.0[build=*_1]', 'ogre==1.10.12[build=*_15]']

conda-forge/win-64                                          Using cache
conda-forge/noarch                                          Using cache
Could not solve for environment specs
The following packages are incompatible
├─ libopenvino-dev 2023.1.0 *_1 is installable and it requires
│  └─ libopenvino-hetero-plugin 2023.1.0 h63175ca_1, which requires
│     └─ pugixml >=1.14,<1.15.0a0 , which can be installed;
└─ ogre 1.10.12 *_15 is not installable because it requires
   └─ pugixml >=1.13,<1.14.0a0 , which conflicts with any installable versions previously reported.

from ironcub-mk1-software.

FabioBergonti avatar FabioBergonti commented on September 13, 2024 1

On my laptop I have

ogre                      1.10.12             ha04c5d8_15    conda-forge

and it works

from ironcub-mk1-software.

antonellopaolino avatar antonellopaolino commented on September 13, 2024 1

I temporarly modified locally the environment.yml file, adding the ogre=1.10.12=*_15 package info and now the installation is successful as anticipated by @traversaro previous comments.

from ironcub-mk1-software.

antonellopaolino avatar antonellopaolino commented on September 13, 2024

How did you create the environment that you used?

I used the command

mamba env create -n <conda-environment-name> --file environment.yml

as indicated in https://github.com/ami-iit/ironcub_mk1_software/tree/FabioBergonti-patch-1#installation-with-conda-linux-and-windows

from ironcub-mk1-software.

antonellopaolino avatar antonellopaolino commented on September 13, 2024

Can you create a new one?

The output is the same exact of before, even changing the environment name and/or performing a mamba clean --all to avoid using cached packages, the ogre version used is always 1.10.12 hbcc8020_2.

from ironcub-mk1-software.

traversaro avatar traversaro commented on September 13, 2024

Interestingly, openvino was migrated to pugixml 1.13 (see conda-forge/openvino-feedstock#37), and indeed 2023.1.0=*_0 has the right metadata (pugixml=1.13, see https://conda-metadata-app.streamlit.app/?q=conda-forge%2Fwin-64%2Flibopenvino-hetero-plugin-2023.1.0-h63175ca_0.conda), but for some reason 2023.1.0=*_1 has the wrong metadata (see https://conda-metadata-app.streamlit.app/?q=conda-forge%2Fwin-64%2Flibopenvino-hetero-plugin-2023.1.0-h63175ca_1.conda).

from ironcub-mk1-software.

traversaro avatar traversaro commented on September 13, 2024

I think we can remove the workaround after conda-forge/ogre-feedstock#111 rebuilt ogre with pugixml 1.14 .

from ironcub-mk1-software.

Related Issues (2)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.