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

Fix conda action boost dependency #1067

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

johnwason
Copy link
Contributor

Attempt to fix the failing conda tests caused by boost dependency error.

@johnwason
Copy link
Contributor Author

@traversaro I am getting another dependency problem from conda: https://github.com/tesseract-robotics/tesseract/actions/runs/12057112091/job/33621028026

@traversaro
Copy link

Interesting, it seems something is still pulling boost-cpp . I will check this tomorrow morning (in Europe). If I do not feel free to ping me.

@traversaro
Copy link

@traversaro I am getting another dependency problem from conda: https://github.com/tesseract-robotics/tesseract/actions/runs/12057112091/job/33621028026

I may be missing something, but those job seem to refer to a commit where boost-cpp is still used? See

.

@johnwason
Copy link
Contributor Author

I grabbed the wrong log link. This is for the branch that uses libboost-devel https://github.com/johnwason/tesseract/actions/runs/12059352095/job/33627810158

@traversaro
Copy link

Ah, ok! The problem is that you are requiring pcl >= 1.14.1 that was built after the libboost 1.86 migration, but also pinning libboost to 1.84 (probably as you depend on the main conda-forge-pinnings)? As the liboost 1.86 migration is quite progressed (and we just build ompl for boost 1.86 as well, see conda-forge/ompl-feedstock#51) probably you can override the conda-forge pinning and pin libboost to 1.86 ?

@johnwason
Copy link
Contributor Author

The script runs conda-smithy as part of the CI process so I don't think we have any pins: https://github.com/johnwason/tesseract/blob/d63aa65982c398b200dbcb4ee67a501605e9d452/.github/workflows/conda.yml#L84

@traversaro
Copy link

The script runs conda-smithy as part of the CI process so I don't think we have any pins: https://github.com/johnwason/tesseract/blob/d63aa65982c398b200dbcb4ee67a501605e9d452/.github/workflows/conda.yml#L84

I guess you get the conda-forge global binnings via conda-smithy, that at the moment are inconsistent as they prescribed to use pcl 1.4.1 and boost 1.84, but in conda-forge it is not a problem as all packages using pcl have been migrated to boost 1.86. To override the conda-smithy pinnings, you can add a conda_build_config.yaml file next to the recipe with the override, where you can override either the boost or pcl pinning.

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

Successfully merging this pull request may close these issues.

2 participants