Can't install cairo-devel and pango-devel on Centos 8.1 (for Tesseract)

Installing cairo-devel and pango-devel on CentOS 8.1 often fails due to dependency conflicts or disabled repositories, particularly when preparing for Tesseract OCR compilation. The primary solution involves enabling the PowerTools repository via dnf config-manager and ensuring all base packages are updated before attempting the installation again.

Understanding the Dependency Conflict

The error typically stems from a missing or disabled repository rather than a broken package. In CentOS 8, development libraries such as those required by Tesseract are not always included in the default BaseOS or AppStream repositories. Specifically, cairo-devel and pango-devel reside in the "PowerTools" (formerly "CodeReady Builder") repository. If this repository is disabled, the package manager cannot resolve the dependencies, leading to transaction failures.

This issue is distinct from general update failures seen in other distributions like Nobara, where protected packages might block operations. As discussed in our guide on Yum/DNF Update Fails: The Operation Would Result in Removing the Following Protected Packages: nobara-amdgpu-config, repository misconfigurations can cause similar semantic errors, though the root cause here is specifically the absence of the development tools repo.

Enabling the PowerTools Repository

To resolve the immediate installation failure, you must explicitly enable the PowerTools repository. This repository contains the build-time dependencies necessary for compiling software from source, including the graphics libraries needed by Tesseract.

1. Check Current Status: First, verify if the PowerTools repository is enabled by running:

   dnf repolist

   Look for a line containing "powertools". If it is absent or marked as disabled, proceed to the next step.
2. Enable the Repository: Use the following command to enable the repository permanently:

   dnf config-manager --set-enabled powertools

   On some minimal installations, you may need to install dnf-utils first if the config-manager subcommand is unavailable.
3. Clean Metadata: Clear the local cache to ensure DNF fetches the latest metadata from the newly enabled source:

   dnf clean all

Alternative Method: Manual Configuration

If the config-manager approach fails, you can manually edit the repository configuration files located in /etc/yum.repos.d/. Look for the file named CentOS-PowerTools.repo (or similar). Ensure that the enabled=1 directive is set within the [powertools] section. Save the file and run dnf makecache to refresh the index.

Updating System Packages

Before installing new development headers, it is crucial to ensure your system is up-to-date. Outdated base packages can conflict with newer development libraries, causing dependency resolution loops. Run the following command to update all installed packages:

dnf update -y

This process ensures that shared libraries like libpng, freetype, and fontconfig are at compatible versions. Failure to update the base system first is a common pitfall that leads to unclear dependency errors, similar to those described in Unclear Answer to 'yum check dependencies' Command in Tech Support. By keeping the base system current, you minimize the risk of circular dependencies during the installation of specialized tools like Tesseract.

Installing Tesseract Dependencies

Once the PowerTools repository is enabled and the system is updated, you can proceed with installing the specific development packages. For Tesseract OCR, you generally need the core libraries along with their development headers.

sudo dnf install cairo-devel pango-devel tesseract-devel

If you are building Tesseract from source, you will also need the standard build tools. Install these using:

sudo dnf groupinstall "Development Tools"

This group includes gcc, make, and cmake, which are essential for the compilation process. After installing these packages, verify the installation by checking the version of the libraries:

pkg-config --modversion cairo

pkg-config --modversion pango

Troubleshooting Remaining Issues

If the installation still fails after enabling PowerTools, consider the following diagnostic steps:

• Check for Conflicting Repositories: Sometimes, third-party repositories (like EPEL) can introduce conflicts. Ensure EPEL is installed and enabled:

  sudo dnf install epel-release

• Verify Package Availability: Search for the specific package to confirm it exists in the enabled repos:

  dnf search cairo-devel

• Review Transaction History: If previous failed attempts left the database in an inconsistent state, use:

  dnf history rollback

  to revert any partial transactions.

In rare cases, disk space issues or permission errors can mimic dependency problems. Always check available disk space with df -h and ensure you have root privileges when modifying system packages.

Frequently Asked Questions

Why does yum check dependencies give unclear answers?

Vague dependency errors often occur when multiple repositories provide conflicting versions of the same library. Running dnf history can help identify recent changes that broke the dependency tree, allowing you to roll back or adjust repository priorities.

Is it safe to enable the PowerTools repository on production servers?

Yes, enabling PowerTools is safe and recommended for systems requiring compilation tools. It does not change default behavior unless explicitly requested, and it only adds development packages that are not part of the standard runtime environment.

How do I forward yum logs for better debugging?

If installation failures persist, forwarding logs to a remote server helps analyze patterns. You can configure rsyslog to send /var/log/yum.log to a central logging server, as detailed in our guide on How to Forward /var/log/yum.log to Remote Logging Server using rsyslog.conf?.

Can I install Tesseract without cairo-devel?

No, cairo is a core rendering backend for Tesseract. Without cairo-devel, the compilation process will fail because Tesseract relies on Cairo for image processing and text recognition features.

What should I do if CentOS 8 reaches End of Life?

CentOS 8 has reached its end-of-life date. For long-term stability, consider migrating to Rocky Linux or AlmaLinux, which maintain compatibility with CentOS 8 packages but offer extended support lifecycles and active community maintenance.