rejecteddepends

Rejecteddepends is a term used in software packaging and dependency resolution to describe a dependency that the resolver cannot satisfy under the current set of constraints. It is not a universal standard across all ecosystems, but it is used in some systems and logs to indicate a specific failure point in the resolution process.

The concept arises when dependency graphs contain constraints that cannot be met simultaneously. Causes include version constraints (for example, a package requires a minimum version that is not available in the repository), conflicts between packages, architecture or platform restrictions, or the removal or deprecation of a required package. In some tools, information about rejected dependencies is recorded in diagnostic output or internal logs to aid debugging and maintenance.

Mechanics: When the resolver evaluates a candidate dependency, it must decide whether to accept or reject it. If no acceptable candidate can be found that satisfies all constraints, the dependency is marked as rejected. The resolver may backtrack to explore alternative versions, propose pinning certain components, or suggest removing conflicting packages. If no resolution is possible, the installation or upgrade fails and an error is reported.

Impact and handling: Rejecteddependencies typically block installation or updates until the underlying constraints are resolved. Users can address them by adjusting repository sources, updating constraint specifications, resolving conflicts between packages, or removing a problematic package or dependency chain.

Relation: Rejecteddepends relates to broader concepts in dependency management, including unsatisfied dependencies, dependency conflicts, backtracking algorithms, and the satisfiability problem as it applies to dependency graphs. See also dependency resolution, package management, and diagnostic logging.