Rebuild 0.15 to align missing pins#79
Rebuild 0.15 to align missing pins#79diegoferigo-rai wants to merge 13 commits intoRoboStack:mainfrom
Conversation
This enables producing a better automated diff with upstream conda_build_config.yaml
|
Moving this comment here for visibility: @traversaro @Tobias-Fischer - do you have any insight into why this PR, which doesn't appear to introduce any functional changes yet, is now failing to build? I would expect it to behave as: |
The build and host environments do not use any kind of lockfile. The only thing ensuring reproducibility are the pinning. In this specific case, the build are failing for exactly the same reason for which: is failing with error: earlier build worked fine as shaderc 2026.2 was not released (see conda-forge/shaderc-feedstock#23), so The proper way to fix this is:
The fast way is to pin shaderc to 2026.1 here. : ) |
|
The build with shaderc 2026.1 fails with: probably it is just easier to ensure that shaderc is properly pinned at conda-forge level. |
Replaces #78 since mutex bump likely messed up GitHub Actions cache.
This PR aims to fully address the problem discussed in:
0.14.0) #77Given that this change does not introduce any revision bumps, I do not anticipate build failures or platform-specific regressions.
I also introduced a new pixi task that prints the diff against the YAML from
conda-forge-pinning-feedstock. This is intended to improve visibility into divergence from upstream pinning and make maintenance of the custom YAML more explicit.pixi run conda-build-config-upstream-diff
The generated diff includes updates beyond the assimp
changes.@traversaro @Tobias-Fischer could you take a look and advise which of these additional changes are appropriate to include in this minor rebuild?