From ArchWiki
Revision as of 20:01, 1 November 2011 by Trusktr (Talk | contribs) (Installing package groups)

Jump to: navigation, search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Template:Article summary start Template:Article summary text Template:Article summary heading Template:Article summary text Template:Article summary heading Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary heading Template:Article summary link Template:Article summary link Template:Article summary link Template:Article summary link Template:Article summary end

The pacman package manager is one of the main features of Arch Linux. It combines a simple binary package format with an easy-to-use build system (see makepkg and Arch Build System). The goal of pacman is to make it possible to easily manage packages, whether they are from the official Arch repositories or the user's own builds.

pacman keeps the system up to date by synchronizing package lists with the master server. This server/client model also allows you to download/install packages with a simple command, complete with all required dependencies.

pacman is written in the C programming language and uses the Template:Filename package format.

Tip: The official pacman package contains also other useful tools, such as makepkg, pactree, vercomp and more. You can get the full list from Template:Codeline


pacman configuration is located in Template:Filename. This is the place where the user configures the program to work in the desired manner. In-depth information about the configuration file can be found in man pacman.conf.

General options

General options are in the Template:Codeline section. Read the man page or look in the default Template:Filename for information on what can be done here.

Skip package from being upgraded

To skip upgrading a specific package, specify it as such:


For multiple packages use a space-separated list, or use additional IgnorePkg lines.

Skip package group from being upgraded

As with packages, skipping a whole package group is also possible:



This section defines which repositories to use, as referred to in Template:Filename. They can be stated here directly, or included from another file.

All official repositories use the same Template:Filename file which uses the Template:Codeline variable, making it necessary to maintain only one list.

The following is an example for the official repositories that defers mirrors to the mirrorlist.

# Add your preferred servers here, they will be used first

# Add your preferred servers here, they will be used first

# Add your preferred servers here, they will be used first
Note: Care should be taken when using the Template:Codeline repository. It is in active development and updating may cause some packages to stop working. People who use the Template:Codeline repository are encouraged to subscribe to the arch-dev-public mailing list for current information.
Warning: Pacman currently uses unsigned packages; however, package signing is in development.


To read other examples of what pacman can do, refer to man pacman. The examples below are just a small sample of operations that can be performed.

Installing packages

Installing specific packages

To install a single package or list of packages (including dependencies), issue the following command:

# pacman -S package_name1 package_name2 ...

Sometimes there are multiple versions of a package in different repositories (e.g. extra and testing). Specify which one to install:

# pacman -S extra/package_name
# pacman -S testing/package_name

Installing package groups

Some packages belong to a group of packages that can all be installed simultaneously. For example, issuing the command

# pacman -S gnome

will install all the packages that belong to the "gnome" group. You can see what packages belong to the gnome group by running:

# pacman -Sg gnome

You can also visit to see what package groups are available.

Note: If a package in the list is already installed on the system, it will be reinstalled even if it is already up-to-date, unless you use the Template:Codeline option.
Warning: Do not refresh the package list when installing packages (i.e. Template:Codeline); this can lead to dependency issues.[1] Upgrade explicitly first; before installing new packages.

Removing packages

To remove a single package, leaving all of its dependencies installed:

# pacman -R package_name

To remove a package and its dependencies which are not required by any other installed package:

# pacman -Rs package_name

To remove a package, its dependencies and all the packages that depend on the target package:

Warning: This operation is recursive, and must be used with care since it can remove many potentially needed packages.
# pacman -Rsc package_name

pacman saves important configuration files when removing certain applications and names them with the extension: Template:Filename. To prevent the creation of these backup files use the Template:Codeline option:

# pacman -Rn package_name
Note: pacman will not remove configurations that the application itself creates (for example "dotfiles" in the home folder).

Upgrading packages

pacman can update all packages on the system with just one command. This could take quite a while depending on how up-to-date the system is. This command can synchronize the repository databases and update the system's packages:

# pacman -Syu
Warning: Instead of immediately updating as soon as updates are available, users must recognize that due to the nature of Arch's rolling release approach, an update may have unforeseen consequences. This means that it is not wise to update if, for example, one is about to deliver an important presentation. Rather, update during free time and be prepared to deal with any problems that may arise.

pacman is a powerful package management tool, but it does not attempt to handle all corner cases. Read The Arch Way if this confuses you. Rather, users must be vigilant and take responsibility for maintaining their own system. When performing a system update it is essential that users read all information output by pacman and use common sense. If a configuration file that you have modified needs to be upgraded for a new version of a package, pacman will prompt you to merge a pacnew file.

Tip: Remember that pacman's output is logged in Template:Filename.

Before upgrading, it is advisable to visit the Arch Linux home page to check the latest news (or subscribe to the RSS feed): when updates require out-of-the-ordinary user intervention (more than what can be handled simply by following the instructions given by pacman), an appropriate news post will be made.

If you encounter problems that cannot be solved by these instructions, make sure to search the forum. It is likely that others have encountered the same problem and have posted instructions for solving it.

Querying package databases

pacman queries the local package database with the -Q flag; see:

$ pacman -Q --help

and queries the sync databases with the -S flag; see:

$ pacman -S --help

pacman can search for packages in the database, searching both in packages' names and descriptions:

$ pacman -Ss string1 string2 ...

To search for already installed packages:

$ pacman -Qs string1 string2 ...

To display extensive information about a given package:

$ pacman -Si package_name

for locally installed packages:

$ pacman -Qi package_name

Passing two Template:Codeline flags will also display the list of backup files and their modification states:

$ pacman -Qii package_name

To retrieve a list of the files installed by a package:

$ pacman -Ql package_name

One can also query the database to know which package a file in the file system belongs to:

$ pacman -Qo /path/to/a/file

To list all packages no longer required as dependencies (orphans):

$ pacman -Qdt

Additional commands

Upgrade the system and install a list of packages (one-liner):

# pacman -Syu package_name1 package_name2 ...

Download a package without installing it:

# pacman -Sw package_name

Install a 'local' package that is not from a repository:

# pacman -U /path/to/package/package_name-version.pkg.tar.xz

Install a 'remote' package (not from a repository):

# pacman -U

Clean the package cache of packages that are not currently installed (Template:Filename):

Warning: Only do this when you are sure that the current versions of installed packages are stable and you will not need to downgrade as Template:Codeline removes all the old versions of installed packages.
# pacman -Sc

Clean the entire package cache:

Warning: This clears the entire package cache. Doing this is a very bad practice, as you will not be able to downgrade to the current set of packages in the case that you upgrade and it causes breakage.
# pacman -Scc

Partial upgrades are unsupported

Arch Linux is a rolling release, and new library versions will be pushed to the repositories. The developers and trusted users will rebuild all the packages in the repositories that need to be rebuilt against the libraries. If you have locally installed packages (such as AUR packages), you will need to rebuild them yourself when their dependencies receive a soname bump.

This means that partial upgrades are not supported. Do not use Template:Codeline or any equivalent such as Template:Codeline and then Template:Codeline. Always upgrade before installing a package if you have refreshed the sync repositories. You should also be very careful when using IgnorePkg/IgnoreGroup for the same reason.

If you do a partial upgrade and binaries are broken because they cannot find the libraries they are linked against, do not "fix" the problem simply by symlinking. Libraries receive soname bumps when they are not backwards compatible. A simple Template:Codeline to a properly synced mirror will fix the issue as long as pacman is not broken.











See also