Skip to content

check-deps: no strict channel priority, like the builds - #57

Merged
Tobias-Fischer merged 1 commit into
mainfrom
no-strict-priority
Oct 10, 2026
Merged

Tobias-Fischer merged 1 commit into
mainfrom
no-strict-priority

Conversation

@Tobias-Fischer

Copy link
Copy Markdown
Collaborator

With strict channel priority, a package found in an earlier channel hides every build of it in later channels. With the shared test channel, which holds all distributions, in front of a release channel, humble's and jazzy's ros2-ros-base couldn't be solved on win-64: the test channel has only lyrical's ros2-pybind11-vendor, which hides humble's and jazzy's (see the mutex check in #54).

  • The builds already pass --channel-priority disabled (rattler_build() in tools/robostack.py).
  • The dependency check (check_dependency_compat.py, rs <d> check-deps) was the only solve in the tooling still using rattler-build's default, strict. It now passes --channel-priority disabled too.
  • By default it only reads conda-forge, so results don't change today. Lyrical linux-64 reports the same libcamera note and visp conflict with and without the change. The difference matters as soon as --channel adds a second channel.

🤖 Generated with Claude Code

With strict priority, a package found in an earlier channel hides every build
of it in the later ones; with the shared test channel (all distributions)
in front of a release channel, humble's and jazzy's win-64 ros2-ros-base
couldn't be solved (the test channel only has lyrical's
ros2-pybind11-vendor). The builds already pass --channel-priority disabled;
the dependency check now does too.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Tobias-Fischer
Tobias-Fischer merged commit c6c3ca2 into main Oct 10, 2026
23 checks passed
@Tobias-Fischer
Tobias-Fischer deleted the no-strict-priority branch October 10, 2026 08:36
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.

1 participant