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

apt upgrade halts with unmet dependencies and held broken packages, delaying patch windows and security compliance.

Environment & Reproduction

Common when mixing PPAs, custom pins, or partial upgrades on Ubuntu 16.04. Reproduce by pinning incompatible library versions.

Root Cause Analysis

Package dependency constraints cannot be satisfied with currently pinned or available versions across enabled repositories.

Quick Triage

Run apt-mark showhold and apt-cache policy for conflicting packages. Simulate resolution with apt -o Debug::pkgProblemResolver=yes install -f.

Step-by-Step Diagnosis

Inspect /etc/apt/preferences and .d pin files, map dependency chains with apt-rdepends, and identify repositories introducing version skew.

Illustrative mockup for ubuntu-16-04-lts — ubuntu1604-b01-p15-diagnosis
apt reports unmet dependencies and held packages — Illustrative mockup — Progressive Robot

Solution – Primary Fix

Unhold or repin conflicting packages to compatible versions, remove problematic PPA sources, then run apt update and apt -f install.

Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Illustrative mockup for ubuntu-16-04-lts — ubuntu1604-b01-p15-fix
pinning adjusted and dependency graph resolved — Illustrative mockup — Progressive Robot

Solution – Alternative Approaches

Freeze current state and backport only critical patches manually, or migrate workload to a supported release with coherent dependency set.

Verification & Acceptance Criteria

apt upgrade completes without dependency errors and critical services remain functional after package changes.

Rollback Plan

Reapply previous pinning and package versions from snapshot or apt logs if application compatibility regresses.

Prevention & Hardening

Limit external repositories, enforce pinning policy review, and test upgrades in staging before production rollouts.

Frequently coupled with dpkg interrupted states and NO_PUBKEY from third-party repositories.

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

View all Ubuntu 16.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

apt_preferences(5), apt-mark(8), and dependency management best practices for legacy Ubuntu environments.

Need Expert Help?

If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.