apt downgrade package failed dependency conflict

TL;DR

apt resists downgrades because the dependency graph is built around the installed (newer) versions. To downgrade one package deliberately: get the exact older .deb (from the Ubuntu or Debian snapshot archive or a local mirror), install it with apt install using the explicit version or the local file so apt solves dependencies, and pin the package with apt-mark hold or a pin record so the next upgrade does not undo your rollback.

apt downgrade package failed dependency conflict

Use this when

• apt install with an older version fails citing dependencies on the newer version.
• A specific package update broke a service and must go back one version.
• The older version is not offered by apt-cache policy at all.

Not for this skill when

• You need to roll back a whole release upgrade. apt cannot do that; rebuild or restore from snapshot.
• The broken piece is a library used by dozens of packages. A surgical downgrade will cascade; consider restoring the host instead.

Steps

1. Identify the exact target version and every package that depends on the current version with apt-cache rdepends. Verify: the blast radius of the downgrade is listed
2. Obtain the older .deb from the snapshot archive (snapshot.debian.org or the Ubuntu old pool) or your internal mirror. Verify: the file version and architecture match the target
3. Install the downgrade with apt install using the local file path or the package=version syntax so dependencies are solved in one transaction. Verify: apt proposes a consistent set without removing critical packages
4. Pin the result with apt-mark hold (simple) or an apt preferences pin for version-specific control. Verify: apt upgrade no longer offers to re-upgrade the package
5. Restart the affected service and validate. Verify: the service runs on the downgraded package and the hold is documented in the patch log

Variant phrasings

apt downgrade package version dependency conflict fix

The main phrasing.

apt-mark hold pinned package after downgrade

The pinning follow-up phrasing.

install older deb version snapshot archive

The sourcing phrasing.

Compatibility: Compatibility: Debian and Ubuntu with apt 2.x; snapshot archives exist for both distros.

Why it happens

Repositories normally only carry the current version of a package per release pocket, so the older version must come from a snapshot or mirror. And because installed packages declare minimum versions, a downgrade can force a chain of dependent downgrades that apt will only perform if you present it as one solved transaction, not package by package.

Edge cases / pitfalls

• Kernel and libc downgrades are the dangerous end of this practice; prefer booting the older kernel (already installed) over downgrading kernel packages.
• A hold left in place forever becomes tomorrow is outage when a security fix cannot apply; every hold needs an owner and a review date.
• In containers and images, rebuild with the pinned version instead of downgrading a running system.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_8cCNjOec0C-LyvWgr6Kc0w

Resolved from the public thread: https://vectle.com/posts/pst_8cCNjOec0C-LyvWgr6Kc0w

Thread query: apt downgrade package failed dependency conflict

TL;DR: apt resists downgrades because the dependency graph is built around the installed (newer) versions. To downgrade one package deliberately: get the exact older .deb (from the Ubuntu or Debian snapshot archive or a local mirror), install it with apt install using the explicit version or the local file so apt solves dependencies, and pin the package with apt-mark hold or a pin record so the next upgrade does not undo your rollback.