How to Use Pacman Commands on Manjaro

Manjaro Linux, based on the Arch Linux distribution, has become increasingly popular due to its stability, versatility, and user-friendly approach. At the heart of Manjaro’s package management system lies Pacman, a powerful command-line tool that enables users to install, update, and maintain software on their systems. This comprehensive guide will walk you through everything you need to know about using Pacman commands effectively on Manjaro Linux, from basic operations to advanced techniques.

Understanding the Pacman Package Manager

Pacman (Package Manager) is the default package management utility for Arch Linux and its derivatives like Manjaro. It combines a simple binary package format with an easy-to-use build system, allowing users to easily manage their software packages.

What Makes Pacman Special?

Pacman handles everything from installing new packages to upgrading your entire system with just a few commands. Its distinguishing features include:

• Simple command syntax that’s easy to remember
• Fast and efficient package handling
• Comprehensive dependency resolution
• Support for package groups and repositories
• Ability to synchronize your local package database with remote repositories

The basic anatomy of a Pacman command follows this structure: pacman [options] [operation] [package_name]. While Manjaro also offers Pamac, a graphical front-end for Pacman, learning the command-line interface provides more control and understanding of your system.

Pacman’s main configuration file is located at /etc/pacman.conf, which contains important settings like repository definitions, package cache location, and various other options.

Getting Started with Pacman

Before diving into specific commands, let’s understand some fundamentals of using Pacman on Manjaro Linux.

Understanding Root Privileges

Most Pacman operations that modify the system require root privileges. You’ll typically need to prefix commands with sudo like this:

sudo pacman -S package_name

Basic Command Structure

Pacman commands consist of an operation flag (uppercase letter) often followed by additional option flags (lowercase letters) to modify the operation’s behavior.

For instance, the three core Pacman commands are:

• -Q (query) – Search the local package database
• -S (sync) – Install or update packages from repositories
• -R (remove) – Uninstall packages from your system

Accessing Help Documentation

If you’re ever unsure about a command or option, Pacman provides comprehensive help:

pacman --help
man pacman

Essential System Update Commands

Keeping your Manjaro system updated is crucial for security and stability. Pacman makes this process straightforward with a few simple commands.

Syncing the Package Database

Before performing any updates, it’s important to refresh your local package database with the latest information from the repositories:

sudo pacman -Syy

This command synchronizes your local package database with the remote repositories, ensuring you have the most current package information.

Updating Your Entire System

To update all installed packages on your system to their latest versions, use:

sudo pacman -Syu

This comprehensive command combines three operations:

• -S for synchronize
• -y to refresh the package database
• -u to upgrade all outdated packages

Running this command regularly (weekly is recommended) helps keep your system secure and stable.

Partial Updates and Specific Package Updates

While it’s generally recommended to update the entire system, you can update specific packages:

sudo pacman -S package_name

However, be cautious with partial updates as they can sometimes lead to dependency issues. It’s best practice to regularly perform full system updates rather than selectively updating packages.

Excluding Packages from Updates

Sometimes you might want to update everything except certain packages:

sudo pacman -Syu --ignore=package_name

This is useful when you need to keep a specific package version for compatibility reasons.

Searching and Installing Packages

Finding and installing software is one of the most common tasks you’ll perform with Pacman. Let’s explore the various commands available for these operations.

Searching for Packages

To search for packages in the Manjaro repositories:

pacman -Ss keyword

This command searches through the repository database for packages matching your keyword in their name or description. The search is case-insensitive and returns partial matches.

For a more targeted search of already installed packages:

pacman -Qs keyword

Installing Packages

To install a package on your system:

sudo pacman -S package_name

You can also install multiple packages simultaneously by separating their names with spaces:

sudo pacman -S package1 package2 package3

Installing Package Groups

Manjaro organizes related packages into groups for easier installation. To install a group:

sudo pacman -S group_name

For example, to install the GNOME desktop environment:

sudo pacman -S gnome

When installing a group, Pacman will prompt you to select which packages from the group you want to install.

Downloading Without Installing

If you just want to download a package without installing it:

sudo pacman -Sw package_name

This downloads the package to the Pacman cache directory (/var/cache/pacman/pkg/) for later use.

Removing Packages and Cleaning the System

Properly removing unused software keeps your system clean and optimized. Pacman offers several methods for package removal with varying levels of thoroughness.

Basic Package Removal

To remove a single package:

sudo pacman -R package_name

This command removes the package but leaves behind any dependencies that were installed with it.

Removing Packages with Dependencies

For a more thorough removal that includes dependencies no longer needed by other packages:

sudo pacman -Rs package_name

The -s flag tells Pacman to remove dependencies that aren’t required by other installed packages.

Complete Package Removal

To remove a package along with all its dependencies and configuration files:

sudo pacman -Rns package_name

This is the most thorough removal option:

• -n removes configuration files
• -s removes dependencies

Finding and Removing Orphaned Packages

Orphaned packages are dependencies that were installed automatically but are no longer required by any package. To identify these:

pacman -Qdt

And to remove all orphaned packages in one command:

sudo pacman -Rns $(pacman -Qdtq)

This powerful command identifies all orphaned packages and removes them completely, including their configuration files.

Querying Package Information

Pacman provides robust capabilities for obtaining information about installed packages and the system state.

Listing Installed Packages

To see all installed packages on your system:

pacman -Q

For a more detailed list with version numbers and descriptions:

pacman -Qi

Finding Specific Package Information

To get detailed information about a specific package:

pacman -Qi package_name

This command displays comprehensive information including version, dependencies, install date, size, and description.

Listing Files Owned by a Package

To see all files installed by a specific package:

pacman -Ql package_name

This is useful when you need to locate configuration files or executables installed by a package.

Finding Which Package Owns a File

If you have a file and want to know which package it belongs to:

pacman -Qo /path/to/file

This command helps identify the source of specific files on your system.

Distinguishing Between Types of Packages

Pacman allows you to filter packages by their installation method:

pacman -Qe   # Explicitly installed packages
pacman -Qd   # Packages installed as dependencies
pacman -Qm   # Packages installed from AUR or manually
pacman -Qn   # Packages installed from the main repositories

These queries help you understand how packages came to be on your system.

Package Cache Management

Pacman keeps a cache of downloaded packages in /var/cache/pacman/pkg/, which can grow quite large over time. Managing this cache is important for system maintenance.

Understanding the Package Cache

The package cache stores:

• Currently installed package versions
• Previously installed package versions
• Downloaded but not installed packages

This cache allows you to reinstall or downgrade packages without redownloading them.

Clearing the Package Cache

To remove all cached packages that aren’t currently installed:

sudo pacman -Sc

For a more aggressive approach that removes all packages from the cache:

sudo pacman -Scc

Be cautious with the latter command, as it removes the ability to downgrade or reinstall packages without downloading them again.

Using paccache for Selective Cleaning

The paccache tool provides more nuanced cache management:

sudo paccache -r          # Remove all but the 3 most recent versions
sudo paccache -rk 1       # Keep only 1 version of each package
sudo paccache -ruk0       # Remove all uninstalled packages

This tool is part of the pacman-contrib package and offers more fine-grained control over cache cleaning.

Working with Package Files

Sometimes you need to work directly with package files rather than installing from repositories. Pacman supports these operations too.

Installing Local Package Files

To install a package file that you’ve downloaded:

sudo pacman -U /path/to/package.pkg.tar.zst

You can also install package files directly from URLs:

sudo pacman -U https://example.com/path/to/package.pkg.tar.zst

Extracting Information from Package Files

To view information about a package file without installing it:

pacman -Qip /path/to/package.pkg.tar.zst

To list the files contained in a package file:

pacman -Qlp /path/to/package.pkg.tar.zst

Managing Manjaro Mirrors

Manjaro pulls packages from mirror servers around the world. Selecting fast and up-to-date mirrors improves download speeds and reliability.

Understanding Mirror Lists

Manjaro’s mirror list is located at /etc/pacman.d/mirrorlist. This file determines which servers Pacman uses to download packages.

Optimizing Your Mirrors

Manjaro provides a dedicated tool called pacman-mirrors to help optimize your mirror list:

sudo pacman-mirrors --fasttrack

This command tests available mirrors and creates a new mirror list with the fastest servers for your location.

For more control, you can specify a country or region:

sudo pacman-mirrors --country United_States,Canada

After updating your mirrors, always refresh the package database:

sudo pacman -Syy

Advanced Pacman Operations

As you become more comfortable with Pacman, you might need more sophisticated operations for system maintenance.

Force Reinstalling a Package

To reinstall a package even if it’s already up to date:

sudo pacman -S --needed package_name

The --needed flag ensures the package is only reinstalled if the versions differ.

Downgrading Packages

If a package update causes problems, you can downgrade to a previous version from the cache:

sudo pacman -U /var/cache/pacman/pkg/package-old_version.pkg.tar.zst

Handling Package Conflicts

When packages conflict, you can force an installation:

sudo pacman -S --overwrite "*" package_name

Use this with caution as it can override important files owned by other packages.

Verifying System Integrity

To check that all installed packages have the required files:

sudo pacman -Qk

For a more thorough verification including file properties:

sudo pacman -Qkk

Pacman vs. Pamac: When to Use Each

Manjaro offers both Pacman (command-line) and Pamac (graphical interface) for package management. Understanding when to use each tool can enhance your experience.

Command-Line vs. Graphical Interface

Pacman provides:

• Speed and efficiency for power users
• Scriptability for automation
• Full control over all operations

Pamac offers:

• User-friendly interface
• Integrated AUR support
• Snap and Flatpak integration
• Search and browse functionality

When to Use Pacman

Pacman is preferable when:

• Performing system maintenance from a terminal
• Working with servers or headless systems
• Troubleshooting package issues
• Writing maintenance scripts

When to Use Pamac

Pamac works better for:

• New Linux users uncomfortable with the command line
• Browsing available packages
• Managing AUR packages alongside repository packages
• Handling Snap or Flatpak packages

While some users suggest exclusively using Pamac on Manjaro to avoid potential compatibility issues, both tools access the same underlying package system and can be used effectively.

Comprehensive Pacman Commands Cheat Sheet

Here’s a quick reference guide to essential Pacman commands for daily use:

System Update Commands:

• sudo pacman -Sy – Sync databases
• sudo pacman -Syy – Force sync databases
• sudo pacman -Syu – Update system
• sudo pacman -Syyu – Force sync and update

Search Commands:

• pacman -Ss keyword – Search repositories
• pacman -Qs keyword – Search installed packages

Installation Commands:

• sudo pacman -S package – Install a package
• sudo pacman -S package1 package2 – Install multiple packages
• sudo pacman -U file.pkg.tar.zst – Install a local package

Removal Commands:

• sudo pacman -R package – Remove a package
• sudo pacman -Rs package – Remove with dependencies
• sudo pacman -Rns package – Remove with dependencies and configs

Query Commands:

• pacman -Q – List installed packages
• pacman -Qi package – Show package info
• pacman -Ql package – List files owned by package
• pacman -Qo /path/to/file – Find package owning file

Cache Commands:

• sudo pacman -Sc – Clear package cache
• sudo pacman -Scc – Clear complete cache

Troubleshooting Common Pacman Issues

Even with a well-designed package manager like Pacman, issues can occasionally arise. Here are solutions to common problems.

Failed to Synchronize Databases

If you encounter “failed to synchronize databases” errors:

1. Check your internet connection
2. Update your mirror list with sudo pacman-mirrors --fasttrack
3. Try manually syncing with sudo pacman -Syy

Handling Key Verification Errors

For package signature verification failures:

sudo pacman-key --refresh-keys

If specific keys are problematic:

sudo pacman-key --init
sudo pacman-key --populate manjaro

Resolving Dependency Conflicts

When packages conflict or have dependency issues:

1. Update your entire system first with sudo pacman -Syu
2. Look for conflicting packages with pacman -Qsq package_keyword
3. Consider removing problematic packages before reinstalling

Recovering from Interrupted Operations

If a package installation or update was interrupted:

sudo rm /var/lib/pacman/db.lck
sudo pacman -Syu

This removes the lock file and completes the interrupted operation.

Library Version Issues

If you encounter “version not found” errors like the GLIBC error, you may need to:

1. Boot from a Manjaro live USB
2. Mount your system partition
3. Use pacstrap to reinstall critical system libraries:

   sudo pacman -S arch-install-scripts
   sudo pacstrap -i /mnt glibc lib32-glibc

4. Alternatively, use the static version of Pacman:

   wget https://pkgbuild.com/~eschwartz/repo/x86_64-extracted/pacman-static
   chmod +x pacman-static
   ./pacman-static -Syyu glibc lib32-glibc

Best Practices for Package Management

Following these best practices will help maintain a stable and reliable Manjaro system.

Regular System Updates

Update your system regularly, but not too frequently:

• Once a week is a good balance between security and stability
• Always read update announcements for major changes
• Update during low-usage periods in case troubleshooting is needed

Avoid Partial Updates

Always update your entire system rather than individual packages:

• Use sudo pacman -Syu rather than -Sy followed by -S package
• Partial updates can lead to dependency conflicts and broken packages

Manage Your Package Cache

Maintain your package cache wisely:

• Keep at least the last few versions of packages for potential downgrades
• Use paccache rather than completely clearing the cache
• Consider setting up automatic cache cleanup with systemd timers

Create Snapshots Before Major Updates

Use filesystem snapshots or backups before significant system updates:

• Tools like Timeshift can create system snapshots
• Having backups makes recovery easier if something goes wrong

Use the AUR Responsibly

When using the Arch User Repository (AUR) with helpers like yay or through Pamac:

• Always check PKGBUILDs before installing
• Limit AUR packages to those you truly need
• Be extra cautious updating AUR packages