Repository navigation
jazzy: gz_ogre_next_vendor without shaderc, as in lyrical - #152
Merged
Merged
Conversation
The package only wraps conda-forge's ogre-next (no OGRE-Next build of its own), but kept shaderc from the upstream package.xml. So every shaderc pin change rebuilt it and its 50 dependents (the Gazebo stack, nav2_bringup, the turtlebots, desktop_full, ...), as in the pinning update #94. New build 28 of just this package; its dependents don't need one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Tobias-Fischer
enabled auto-merge (squash)
October 24, 2026 04:40
ABI check (linux-64)jazzy linux-64: 1 can be bumped on their own1 packages can be bumped on their own (no libraries: 1)
Compared with the newest builds on https://conda.anaconda.org/robostack-jazzy/linux-64. About this checkEach package this pull request built, compared with its newest released build (
Exported symbols are compared (the released packages are stripped, so struct layouts aren't); unchanged installed headers rule out layout and inline changes, changed ones are listed for review. Dependents to rebuild are the released ones linking to a changed library. A changed pin is part of the comparison. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
gz_ogre_next_vendoronly wraps conda-forge'sogre-next; the package is 37 KB and builds no OGRE-Next of its own. It still depends onshaderc, carried over from the upstream package.xml. So everyshadercpin change rebuilds it and its 50 dependents (the Gazebo stack, nav2_bringup, the turtlebots, desktop_full and so on). That's the whole jazzy rebuild in the pinning update #94.Lyrical and rolling already drop it (
remove_host/remove_run: ["shaderc"]). This does the same for jazzy and gives just this package build 28. Its dependents don't need a new build: their run dependencies on it don't change.Tested: built locally on osx-arm64.
ros2-gz-ogre-next-vendor 0.0.5 _28has the same dependencies as_27, minusshaderc.After merging: the bot should regenerate #94, and jazzy should then have nothing to rebuild.
🤖 Generated with Claude Code