Debian 10 – full-upgrade blocked by held packages – Fix & Prevention

📖 ~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

full-upgrade fails with unmet dependencies and leaves security updates unapplied.

Environment & Reproduction

Seen after manual package pinning, partial upgrades, or repository mix-ups.

Root Cause Analysis

Held packages and pin priorities block the resolver from selecting required versions.

Quick Triage

List held packages and inspect apt preferences to identify policy conflicts.

Step-by-Step Diagnosis

Use resolver simulation and package audits to isolate exact blockers.

Solution – Primary Fix

Clear unnecessary holds, repair package state, and rerun full-upgrade.

Solution – Alternative Approaches

Disable nonessential third-party repositories while resolving dependency transitions.

Verification & Acceptance Criteria

Upgrade simulation and actual run finish without unresolved or kept-back packages.

Rollback Plan

Reapply required holds and restore previous repository list if compatibility issues arise.

Prevention & Hardening

Track hold justifications and review pinning policies before maintenance windows.

Related Errors & Cross-Refs

Commonly linked to expired repositories, stale pin files, and interrupted upgrades.

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

View all Debian 10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Debian apt policy and package pinning guides.