UnsatisfiableError in conda SAT solver when resolving conflicting package versions
0 reputation · 27 Jul 2025, 11:09 UTC
Goal: receive alerts only when conda reports an UnsatisfiableError during environment creation or update, while avoiding noise from routine channel metadata refresh messages that appear in Navigator or CLI logs.
Constraints: Anaconda Navigator aggregates notifications from conda CLI and GUI, and conda configuration flags such as auto_update and channel_priority affect when solver runs; there is no built‑in filter to separate error‑level events from informational channel updates. Uncertainty: whether enabling libmamba solver changes the verbosity or error messaging, and if logging levels can be tuned per interface.
Can conda be configured to emit only error‑level notifications (e.g., UnsatisfiableError) and suppress INFO‑level channel metadata refresh messages in both CLI and Navigator?
Does switching the solver backend to libmamba alter the verbosity or format of unsatisfiability reports, making them easier to filter?
Is there a setting in .condarc or Anaconda Navigator that allows per‑environment alert thresholds without affecting global auto_update behavior?