Debian 13 Unmet Dependencies During full-upgrade

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

System upgrades stop due to unresolved package dependency chains.

Environment & Reproduction

Often seen with mixed repos or held packages.

Root Cause Analysis

Package holds, stale indices, or conflicting versions create resolver deadlocks.

Quick Triage

Check package holds and candidate versions.

Step-by-Step Diagnosis

Run APT resolver debug mode to locate conflict origin.

Solution – Primary Fix

Remove problematic holds and repair package state before retrying.

Solution – Alternative Approaches

Temporarily remove conflicting packages and reinstall compatible versions.

Verification & Acceptance Criteria

`apt full-upgrade` completes without unresolved dependencies.

Rollback Plan

Re-apply prior holds and repository settings if regressions appear.

Prevention & Hardening

Use repo policy controls and periodic dependency health checks.

Related Errors & Cross-Refs

Related to pin-priority conflicts and partial release transitions.

Related tutorial: View the step-by-step tutorial for Debian 13.

View all Debian 13 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Debian package dependency and upgrade troubleshooting docs.