apt full-upgrade held back by broken dependencies

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

Major package updates are blocked by unmet dependencies and held packages.

Environment & Reproduction

apt reports held broken packages and refuses to resolve upgrade transaction.

Root Cause Analysis

Use apt-cache policy, apt-mark showhold, and simulated install plans to locate conflict origin.

Quick Triage

Mixed repositories or pinned package versions conflict with Ubuntu 26.04 dependency graph.

Step-by-Step Diagnosis

Unhold conflicting packages, remove incompatible third-party repo versions, and run apt –fix-broken install.

Solution – Primary Fix

Execute apt full-upgrade successfully and confirm no residual broken package state.

Solution – Alternative Approaches

Avoid mixing release channels and keep repository priority policy documented.

Verification & Acceptance Criteria

Re-pin previously stable package versions if critical app compatibility requires temporary hold.

Rollback Plan

Run periodic dry-run upgrade checks in CI against representative server images.

Prevention & Hardening

apt-mark showhold; apt –fix-broken install; apt full-upgrade -s; apt-cache policy

Related Errors & Cross-Refs

Provide package solver output and active repository list for dependency triage.

Related tutorial: View the step-by-step tutorial for Ubuntu 26.04 LTS.

View all Ubuntu 26.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

PPA packages often lag LTS transitions and can block base distro dependency resolution.