FreeBSD 13 – pkg upgrade blocked by locked dependency chain

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

pkg upgrade aborts because one or more dependencies are locked.

Environment & Reproduction

Typically appears after emergency pinning of critical packages.

Root Cause Analysis

The solver cannot produce a valid upgrade plan with locked dependency edges.

Quick Triage

List locks and map them against the blocked upgrade transaction.

Step-by-Step Diagnosis

Inspect reverse dependencies and identify only policy-required locks.

Solution – Primary Fix

Temporarily unlock required packages, complete upgrade, then relock if needed.

Solution – Alternative Approaches

Use scoped per-package upgrades during tightly controlled maintenance windows.

Verification & Acceptance Criteria

Upgrade simulation and dependency checks complete without conflicts.

Rollback Plan

Restore lock set and package snapshot if application behavior regresses.

Prevention & Hardening

Track lock owner and expiry in change records to prevent stale constraints.

Related Errors & Cross-Refs

Often overlaps with ABI drift and partial repository sync conditions.

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

View all FreeBSD 13 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

pkg-lock manual and FreeBSD package branch policy notes.