assimp351 migration failing with not-solvable situation

[traversaro]

Solution to issue cannot be found in the documentation.

• [X] I checked the documentation.

Issue

The bot is failing with error:

2023-10-06T11:45:00.7528437Z ['hpp-fcl',
2023-10-06T11:45:00.7530473Z  'hpp-util 4.15.1.*',
2023-10-06T11:45:00.7530921Z  'hpp-environments 4.15.1.*',
2023-10-06T11:45:00.7531352Z  'pinocchio',
2023-10-06T11:45:00.7536611Z  'boost-cpp 1.78.0.*',
2023-10-06T11:45:00.7584890Z  'urdfdom 3.1.*',
2023-10-06T11:45:00.7587449Z  'octomap',
2023-10-06T11:45:00.7589951Z  'tinyxml',
2023-10-06T11:45:00.7592465Z  'libgcc-ng >=12',
2023-10-06T11:45:00.7594995Z  'libstdcxx-ng >=12',
2023-10-06T11:45:00.7597504Z  'eigen',
2023-10-06T11:45:00.7600024Z  'example-robot-data',
2023-10-06T11:45:00.7602555Z  'assimp 5.3.1.*']
2023-10-06T11:45:00.7604958Z 
2023-10-06T11:45:00.7607310Z for channels 
2023-10-06T11:45:00.7609710Z 
2023-10-06T11:45:00.7612227Z ['file:///home/runner/work/_temp/tmpphyw7q89', 'conda-forge', 'msys2']
2023-10-06T11:45:00.7614733Z 
2023-10-06T11:45:00.7617102Z The reported errors are:
2023-10-06T11:45:00.7619525Z 
2023-10-06T11:45:00.7621916Z Could not solve for environment specs
2023-10-06T11:45:00.7624669Z The following packages are incompatible
2023-10-06T11:45:00.7634864Z ├─ assimp 5.3.1.*  is installable with the potential options
2023-10-06T11:45:00.7635285Z │  ├─ assimp 5.3.1, which can be installed;
2023-10-06T11:45:00.7635631Z │  └─ assimp 5.3.1 would require
2023-10-06T11:45:00.7636161Z │     └─ libboost >=1.82.0,<1.83.0a0 , which requires
2023-10-06T11:45:00.7638767Z │        └─ boost-cpp 1.82.0* , which can be installed;
2023-10-06T11:45:00.7641542Z ├─ boost-cpp 1.78.0.*  is not installable because it conflicts with any installable versions previously reported;
2023-10-06T11:45:00.7644295Z └─ hpp-environments 4.15.1.*  is installable with the potential options
2023-10-06T11:45:00.7646912Z    ├─ hpp-environments 4.15.1 would require
2023-10-06T11:45:00.7649649Z    │  └─ hpp-fcl [>=2.2.0,<2.2.1.0a0 |>=2.3.2,<2.3.3.0a0 |>=2.3.5,<2.3.6.0a0 ], which requires
2023-10-06T11:45:00.7652582Z    │     └─ assimp >=5.2.5,<5.2.6.0a0 , which conflicts with any installable versions previously reported;
2023-10-06T11:45:00.7655253Z    └─ hpp-environments 4.15.1 would require
2023-10-06T11:45:00.7657867Z       └─ hpp-fcl >=1.8.1,<1.8.2.0a0  with the potential options
2023-10-06T11:45:00.7660446Z          ├─ hpp-fcl 1.8.1 would require
2023-10-06T11:45:00.7661656Z          │  └─ assimp >=5.2.4,<5.2.5.0a0  with the potential options
2023-10-06T11:45:00.7662167Z          │     ├─ assimp 5.2.4 would require
2023-10-06T11:45:00.7662717Z          │     │  └─ boost-cpp >=1.74.0,<1.74.1.0a0 , which can be installed;
2023-10-06T11:45:00.7663470Z          │     └─ assimp 5.2.4 conflicts with any installable versions previously reported;
2023-10-06T11:45:00.7664027Z          ├─ hpp-fcl 1.8.1 would require
2023-10-06T11:45:00.7664572Z          │  └─ boost >=1.74.0,<1.74.1.0a0 , which requires
2023-10-06T11:45:00.7665125Z          │     └─ boost-cpp 1.74.0.* , which can be installed;
2023-10-06T11:45:00.7665742Z          └─ hpp-fcl [1.8.1|2.2.0|2.3.2|2.3.5], which cannot be installed (as previously explained).

See https://conda-forge.org/status/#assimp531 .

Installed packages

.

Environment info

.

[traversaro]

The problem seems that hpp-fcl does not have updated package for v1. In theory the v1 abi_migration branch was added in https://github.com/conda-forge/hpp-fcl-feedstock/pull/72, but apparently there is no v1 branch in hpp-fcl at the moment: https://github.com/conda-forge/hpp-fcl-feedstock/branches .

[traversaro]

fyi @ymontmarin @jcarpent

[traversaro]

I guess soon we will hit this also in https://conda-forge.org/status/#boost_cpp_to_libboost .

[ymontmarin]

@traversaro Now the whole HPP stack is compatible with hpp-fcl 2.x.x, that is why we do not need to maintain 1.x.x and I discarded the branch.

After looking, I think both pinocchio and hpp-fcl both have builds with assimp 531, but hpp-environments do not because example-robot-data also does not.

Do you know why the migration did not trigger, for example-robot-data ? Should I do it manually ?

[traversaro]

@traversaro Now the whole HPP stack is compatible with hpp-fcl 2.x.x, that is why we do not need to maintain 1.x.x and I discarded the branch.

Ah cool! In that case probably we can remove the lines https://github.com/conda-forge/hpp-fcl-feedstock/blob/6f5e076a81883d1cf1ec3b5f5e84aacdd32a0387/conda-forge.yml#L2-L3 .

After looking, I think both pinocchio and hpp-fcl both have builds with assimp 531, but hpp-environments do not because example-robot-data also does not.

Actually hpp-environments does not depend on assimp, reading better the error it seems that assimp 3.5.1 depends on libboost 1.82, so hpp-environments cannot be installed as it is still depends on libbost 1.78, probably we just need to merge https://github.com/conda-forge/hpp-environments-feedstock/pull/20 then, thanks!

[traversaro]

Fixed thanks to @h-vetinari, see https://github.com/conda-forge/hpp-pinocchio-feedstock/pull/22 and related PRs.