ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal: Recreate an environment defined in an environment.yml file on a macOS developer workstation inside a Linux-based production container with identical package versions and builds. Uncertainty arises because conda resolves platform-specific package builds at install time, channel priority settings can shift package sources, transitive dependencies are re‑
Goal Understand why Bazel emits the error “error: no such package” for a target that appears to have a correct BUILD file, focusing on the analysis phase and how the message varies across Bazel versions. Constraints and uncertainty In Bazel 5.x the error includes the missing package path, whereas Bazel 4.x may omit the path unless the build is run with --ver
Conda selects packages using the channel_priority setting in .condarc, with modes strict, flexible, or disabled. The resolver is documented to prefer channels according to that priority when versions differ. The unresolved behavior concerns identical package versions that appear on multiple channels with different builds. Documentation describes priority for
bazel