Resolving Dependency Conflicts with apt-pin on Debian-Based Systems -

Introduction to Dependency Conflicts

I’ve seen this go wrong when updating packages on Debian-based systems - dependency conflicts can be a real headache. In 2025, many users faced problems with package updates due to these conflicts, and as of 2026, it’s still a crucial issue to understand how to handle them for maintaining a stable and secure system.

Understanding apt-pin

The real trick is using apt-pin to pin packages to specific versions, which can help resolve these conflicts. By pinning a package, you ensure it remains at a specific version, even when newer versions are available. This is particularly useful when a newer version introduces a dependency conflict.

To use apt-pin, you’ll need to create a configuration file in the /etc/apt/preferences.d/ directory. For example, to pin the nginx package to version 1.23.3, you can create a file called nginx-pin with the following contents:

Package: nginx
Pin: version 1.23.3
Pin-Priority: 1001

This ensures the nginx package remains at version 1.23.3, even when newer versions are available.

Practical Examples

Let’s consider a common scenario. You’re running a Debian-based system with the mysql-server package installed. When you try to update the system, you encounter a dependency conflict due to a newer version of the libmysqlclient-dev package. To resolve this, you can pin the libmysqlclient-dev package to the version compatible with the mysql-server package.

First, find the version of the libmysqlclient-dev package compatible with the mysql-server package by checking its dependencies:

apt-cache depends mysql-server

This shows you the dependencies of the mysql-server package, including the version of the libmysqlclient-dev package it requires.

Once you’ve found the compatible version, you can pin it using apt-pin. For example:

Package: libmysqlclient-dev
Pin: version 8.0.28-1
Pin-Priority: 1001

This ensures the libmysqlclient-dev package remains at version 8.0.28-1, compatible with the mysql-server package.

Troubleshooting Notes

This is where people usually get burned - pinning a package can prevent it from receiving security updates, leaving your system vulnerable. To mitigate this risk, regularly review the packages you’ve pinned and update them when possible. Use the apt-cache policy command to check the version of a package and see if newer versions are available:

apt-cache policy libmysqlclient-dev

This shows you the installed version of the libmysqlclient-dev package and any newer versions available.

Security Considerations

Don’t bother with pinning packages without considering the security implications. By pinning a package, you may prevent it from receiving security updates, making your system vulnerable. To minimize risks, pin packages only when necessary and regularly review the packages you’ve pinned. The Debian Security Tracker is a great resource to stay informed about known security vulnerabilities in Debian packages.

Best Practices

In practice, to get the most out of apt-pin and minimize risks, follow these guidelines:

Pin packages only when necessary to resolve dependency conflicts.
Regularly review pinned packages and update them to the latest version when possible.
Use apt-cache policy to check package versions and see if newer versions are available.
Stay informed about known security vulnerabilities using the Debian Security Tracker.

By following these guidelines and using apt-pin judiciously, you can effectively resolve dependency conflicts and maintain a stable and secure Debian-based system.