Update pinnings (mainly assimp 6)#81
Conversation
|
Thanks @diegoferigo-rai! I'd be keen to fix #76 while we are at it .. @diegoferigo-rai @traversaro @eholum would any of you be happy to try @traversaro's suggested patch? |
|
Same error as RoboStack/ros-jazzy#212 (comment) |
|
What do you think we should do here @traversaro ? |
I would just revert the patch to https://github.com/RoboStack/ros-jazzy/blob/main/patch/ros-jazzy-rosidl-generator-py.osx.patch, perhaps by just changing the line |
|
Hi @diegoferigo-rai - are you happy to include the patch suggested by @traversaro, so we can merge here? |
|
Added the patch - @traversaro do you think we should merge? |
Updated dependencies and removed obsolete entries in conda build configuration.
Changed IGNORE_CACHE_AND_DO_FULL_REBUILD to true for testing.
Updated eigen_abi_devel version from '3.4.0' to '5.0.1'.
Updated urdfdom version to 5.1 and added vtk version 9.6.2.
Add urdfdom_headers version 2.1.2 to the configuration.
|
Wow, this ended up being a substantial amount of work! Thanks, @Tobias-Fischer, for driving this forward. It makes me wonder whether the project could leverage copilot cloud agents to create many of these fixes automatically. It seems like a great use case, although I don't have direct experience setting them up and I'm not sure what the current limitations are for open-source projects. |
|
Many of my fixes are thanks to Codex locally. Agreed we might want to give the GitHub agents a go. |
|
That said, as far as I understand GitHub agents are constrained to a single repository, so they would rediscover the same fixes over and over for each distribution .. |
|
Assuming the Windows build passes, are we happy to merge here @traversaro @wep21 @diegoferigo-rai @wolfv? |
Follows up:
that achieved a successful rebuild without updating any package pinning (from #79 (comment)).
Hopefully fixing:
0.14.0) #77