Pacman linux ��� ���

Pacman Home Page

A simple library-based package manager.

Introduction

pacman is a utility which manages software packages in Linux. It uses simple compressed files as a package format, and maintains a text-based package database (more of a hierarchy), just in case some hand tweaking is necessary.

pacman does not strive to «do everything.» It will add, remove and upgrade packages in the system, and it will allow you to query the package database for installed packages, files and owners. It also attempts to handle dependencies automatically and can download packages from a remote server.

History

Version 2.0 of pacman introduced the ability to sync packages (the —sync option) with a master server through the use of package databases. Prior to this, packages would have to be installed manually using the —add and —upgrade operations.

Version 3.0 was the switch to a two-part pacman — a back-end named libalpm (library for Arch Linux Package Management) and the familiar pacman front-end. Speed in many cases was improved, along with dependency and conflict resolution being able to handle a much wider variety of cases. The switch to a library-based program should also make it easier in the future to develop alternative front ends.

Version 4.0 added package signing and verification capabilities to the entire makepkg/repo-add/pacman toolchain via GnuPG and GPGME.

Version 5.0 added support for pre/post-transaction hooks and sync database file list operations.

Documentation

Man Pages

There are several man pages available for the programs, utilities, and configuration files dealing with pacman.

Источник

Pacman

Содержание

Общее

Arch Linux использует менеджер пакетов Pacman, который соединяет в себе простой формат бинарных пакетов и простую в использовании систему сборки, позволяющую пользователям с легкостью управлять и настраивать под себя пакеты, вне зависимости от того, официальные ли они или собранные пользователем. Система репозиториев позволяет пользователям создавать и поддерживать собственные репозитории с собранными пакетами, что способствует росту сообщества.

Pacman может держать систему в новейшем состоянии, синхронизируя пакеты с главным сервером, тем самым позволяя сознательному администратору поддерживать систему. Клиент-серверная модель позволяет скачивать/устанавливать пакеты одной командой со всеми требуемыми зависимостями (похоже на apt-get от Debian).

Pacman был написан на языке C и поэтому он быстрый, легкий. Он использует .tar.gz формат пакетов, эти пакеты извлекаются быстрее.

Использование

Pacman является универсальным менеджером пакетов, способным скачивать, устанавливать и обновлять пакеты и из репозитория, и собственные локальные, удалять и искать их. Вам только необходимо знать, какой ключ используется функцией для желаемых действий. Вот несколько наиболее часто используемых:

Установка и удаление пакетов

Перед установкой и обновлением пакетов полезно синхронизировать базу данных локально установленных пакетов с удалёнными репозиториями

Для того чтобы установить или обновить один пакет или группу пакетов (включая зависимости), используйте следующую команду:

Иногда пакет имеет несколько версий в разных репозиториях (например в extra и testing). Вы можете указать, какой именно вы хотите установить:

Вы можете совмещать параметры, например, эта команда синхронизирует базы данных и установит пакет:

Удалить пакет (оставляя все зависимости в системе):

Удалить пакет со всеми зависимостями, не используемыми другими установленными пакетами:

По умолчанию Pacman создает резервные копии конфигурационных файлов удаляемых приложений с помощью добавления к ним расширения *. pacsave. Если вы хотите удалить эти файлы при удалении соответствующего пакета (подсказка: это операция называется purging в Debian-системах), вы можете использовать:

Конечно, это может быть дополнено -s, чтобы также удалить ненужные теперь зависимости. Таким образом, команда полностью удалит пакет, его конфигурации и все зависимости, которые больше не нужны:

Обновление системы

Pacman может обновить все пакеты системы одной командой. Количество пакетов зависит от того, насколько ваша система современна.

NB: вы можете синхронизировать базы данных репозиториев И обновить все установленные пакеты одной командой:

Хорошо выполнять эту команду каждые несколько дней.

Получение списка установленных пакетов для быстрого восстановления системы

Если ваша система упала и ее сложно восстановить то неплохо бы иметь список пакетов которые были установлены в ней.

Сохранить в файл pkglist список пакетов установленных в системе:

Сохраните этот файл на флешке или еще где-нибудь.

Если вдруг с вашей системой случится что-либо неприятное то установленые пакеты легко можно восстановить:

Запросы к базе данных пакетов

• Поиск пакетов в репозиториях, вы можете указать только часть названия:

• Поиск среди установленных пакетов:

• Вывод информации о пакете:

• Вывод списка файлов пакета:

• Какой пакет является владельцем файла?

• Перечислите все пакеты, больше не требуемые как зависимости(сироты):

• Удалить всех сирот: (Проверьте сначала вывод команды pacman -Qdt.)

Одновременный поиск в репозитории и среди установленных пакетов

Вы можете использовать следующий bash скрипт в качестве эквивалента для одновременного вызова pacman -Ss foo и pacman -Qs foo, для того чтобы узнать, какие из пакетов в выводе установлены на вашей системе. Последние будут помечены звёздочкой.

Сохраните этот скрипт в каталоге, включенном в переменную PATH (например,

/bin/), и назовите его pacsearch. Сделайте его исполняемым с помощью

Теперь если вы напишете, например:

вывод может выглядеть так:

В этом случае вы узнаете, что ни один из вышеперечисленных пакетов (кроме самого qt) на вашей системе не установлен.

NB1: был добавлен запрос на flyspray с предложением интегрировать вышеуказанную функциональность в сам pacman, чтобы ‘грязные’ хитрости bash стали стать ненужными с последующими версиями pacman.

NB2: вы можете изменить этот bash скрипт с помощью этого wiki, для того чтобы установленные пакеты были выделены различными цветами в выводе.

Другое использование

• Скачать пакет, но не устанавливать его:

• Установить локальный пакет (не из репозитория):

Вы можете ввести ссылку:

• Очистка кэша pacman`а (/var/cache/pacman/pkg):

• Для того, чтобы переустановить все пакеты в вашей системе (которые доступны в репозитории):

Для более детальной информацией о возможных ключах обратитесь к pacman —help или man pacman.

Настройка

Настройки pacman`a находятся в /etc/pacman.conf . Важными секциями являются:

Основные опции

Основные опции находятся в секции [options]. Есть одна полезная опция IgnorePkg. Например, если вы изменяли или накладывали патч на пакет, добавление его в IgnorePkg укажет pacman’у не обновлять его при выходе следующей версии пакета. Но pacman всё же предупредит вас о том, что доступна более свежая версия, так что в итоге вы можете обновить ваш изменённый пакет. Опция также полезна для БОЛЬШИХ пакетов (например, openoffice-base), если вы хотите избежать скачивания и обновления всего пакета каждый раз, когда в репозитории появляется маленькое изменение. Поскольку pacman всё равно предупредит вас о последней версии, вы можете обновить пакет вручную.

Репозитории

В этой секции вы указываете используемые репозитории. Они могут быть указаны напрямую или как файл, содержащий список серверов. Последнее удобно для официальных репозиториев, имеющих множество зеркал.

За более подробной информацией обратитесь к man pacman.

Источник

pacman/Tips and tricks

For general methods to improve the flexibility of the provided tips or pacman itself, see Core utilities and Bash.

Contents

Maintenance

This article or section needs expansion.

Listing packages

With version

You may want to get the list of installed packages with their version, which is useful when reporting bugs or discussing installed packages.

• List all explicitly installed packages: pacman -Qe .
• List all packages in the package group named group : pacman -Sg group
• List all foreign packages (typically manually downloaded and installed or packages removed from the repositories): pacman -Qm .
• List all native packages (installed from the sync database(s)): pacman -Qn .
• List all explicitly installed native packages (i.e. present in the sync database) that are not direct or optional dependencies: pacman -Qent .
• List packages by regex: pacman -Qs regex .
• List packages by regex with custom output format (needs expac ): expac -s «%-30n %v» regex .

With size

Figuring out which packages are largest can be useful when trying to free space on your hard drive. There are two options here: get the size of individual packages, or get the size of packages and their dependencies.

Individual packages

The following command will list all installed packages and their individual sizes:

Packages and dependencies

To list package sizes with their dependencies,

• Install expac and run expac -H M ‘%m\t%n’ | sort -h .
• Run pacgraph with the -c option.

To list the download size of several packages (leave packages blank to list all packages):

To list explicitly installed packages not in the meta package base nor package group base-devel with size and description:

To list the packages marked for upgrade with their download size

By date

To list the 20 last installed packages with expac , run:

or, with seconds since the epoch (1970-01-01 UTC):

Not in a specified group, repository or meta package

List explicitly installed packages not in the base meta package:

List explicitly installed packages not in the base meta package or base-devel package group:

List all installed packages unrequired by other packages, and which are not in the base meta package or base-devel package group:

As above, but with descriptions:

List all installed packages that are not in the specified repository repo_name

List all installed packages that are in the repo_name repository:

List all packages on the Arch Linux ISO that are not in the base meta package:

Development packages

To list all development/unstable packages, run:

Browsing packages

To browse all installed packages with an instant preview of each package:

This uses fzf to present a two-pane view listing all packages with package info shown on the right.

Enter letters to filter the list of packages; use arrow keys (or Ctrl-j / Ctrl-k ) to navigate; press Enter to see package info under less.

To browse all packages currently known to pacman (both installed and not yet installed) in a similar way, using fzf, use:

The navigational keybindings are the same, although Enter will not work in the same way.

Listing files owned by a package with size

This one might come in handy if you have found that a specific package uses a huge amount of space and you want to find out which files make up the most of that.

Identify files not owned by any package

If your system has stray files not owned by any package (a common case if you do not use the package manager to install software), you may want to find such files in order to clean them up.

One method is to use pacreport —unowned-files as the root user from pacutils which will list unowned files among other details.

Another is to list all files of interest and check them against pacman:

Tracking unowned files created by packages

Most systems will slowly collect several ghost files such as state files, logs, indexes, etc. through the course of usual operation.

pacreport from pacutils can be used to track these files and their associations via /etc/pacreport.conf (see pacreport(1) § FILES ).

An example may look something like this (abridged):

Then, when using pacreport —unowned-files as the root user, any unowned files will be listed if the associated package is no longer installed (or if any new files have been created).

Additionally, aconfmgr ( aconfmgr-git AUR ) allows tracking modified and orphaned files using a configuration script.

Removing unused packages (orphans)

For recursively removing orphans and their configuration files:

If no orphans were found, the output is error: argument ‘-‘ specified with empty stdin . This is expected as no arguments were passed to pacman -Rns .

Removing everything but essential packages

If it is ever necessary to remove all packages except the essentials packages, one method is to set the installation reason of the non-essential ones as dependency and then remove all unnecessary dependencies.

First, for all the packages installed «as explicitly», change their installation reason to «as dependency»:

Then, change the installation reason to «as explicitly» of only the essential packages, those you do not want to remove, in order to avoid targeting them:

Finally, follow the instructions in #Removing unused packages (orphans) to remove all packages that have installation reason «as dependency».

Getting the dependencies list of several packages

Dependencies are alphabetically sorted and doubles are removed.

Listing changed backup files

The factual accuracy of this article or section is disputed.

If you want to back up your system configuration files, you could copy all files in /etc/ but usually you are only interested in the files that you have changed. Modified backup files can be viewed with the following command:

Running this command with root permissions will ensure that files readable only by root (such as /etc/sudoers ) are included in the output.

Back up the pacman database

The following command can be used to back up the local pacman database:

Store the backup pacman database file on one or more offline media, such as a USB stick, external hard drive, or CD-R.

The database can be restored by moving the pacman_database.tar.bz2 file into the / directory and executing the following command:

Check changelogs easily

When maintainers update packages, commits are often commented in a useful fashion. Users can quickly check these from the command line by installing pacolog AUR . This utility lists recent commit messages for packages from the official repositories or the AUR, by using pacolog

Installation and recovery

Alternative ways of getting and restoring packages.

Installing packages from a CD/DVD or USB stick

This article or section is a candidate for merging with #Custom local repository.

To download packages, or groups of packages:

Pacman, which will reference the host installation by default, will not properly resolve and download existing dependencies. In cases where all packages and dependencies are wanted, it is recommended to create a temporary blank DB and reference it with —dbpath :

Then you can burn the «Packages» folder to a CD/DVD or transfer it to a USB stick, external HDD, etc.

1. Mount the media:

2. Edit pacman.conf and add this repository before the other ones (e.g. extra, core, etc.). This is important. Do not just uncomment the one on the bottom. This way it ensures that the files from the CD/DVD/USB take precedence over those in the standard repositories:

3. Finally, synchronize the pacman database to be able to use the new repository:

Custom local repository

Use the repo-add script included with pacman to generate a database for a personal repository. Use repo-add —help for more details on its usage. A package database is a tar file, optionally compressed. Valid extensions are .db or .files followed by an archive extension of .tar, .tar.gz, .tar.bz2, .tar.xz, .tar.zst, or .tar.Z. The file does not need to exist, but all parent directories must exist.

To add a new package to the database, or to replace the old version of an existing package in the database, run:

The database and the packages do not need to be in the same directory when using repo-add, but keep in mind that when using pacman with that database, they should be together. Storing all the built packages to be included in the repository in one directory also allows to use shell glob expansion to add or update multiple packages at once:

If you are looking to support multiple architectures then precautions should be taken to prevent errors from occurring. Each architecture should have its own directory tree:

The repo-add executable checks if the package is appropriate. If this is not the case you will be running into error messages similar to this:

repo-remove is used to remove packages from the package database, except that only package names are specified on the command line.

Once the local repository database has been created, add the repository to pacman.conf for each system that is to use the repository. An example of a custom repository is in pacman.conf . The repository’s name is the database filename with the file extension omitted. In the case of the example above the repository’s name would simply be repo. Reference the repository’s location using a file:// url, or via FTP using ftp://localhost/path/to/directory.

If willing, add the custom repository to the list of unofficial user repositories, so that the community can benefit from it.

Network shared pacman cache

This article or section is a candidate for merging with Package_Proxy_Cache.

If you happen to run several Arch boxes on your LAN, you can share packages so that you can greatly decrease your download times. Keep in mind you should not share between different architectures (i.e. i686 and x86_64) or you will run into problems.

Read-only cache

If you are looking for a quick solution, you can simply run a standalone webserver, e.g. darkhttpd , which other computers can use as a first mirror:

You could also run darkhttpd as a systemd service for convenience. Just add this server at the top of your /etc/pacman.d/mirrorlist in client machines with Server = http://mymirror:8080 . Make sure to keep your mirror updated.

If you are already running a web server for some other purpose, you might wish to reuse that as your local repository server instead of darkhttpd. For example, if you already serve a site with nginx, you can add an nginx server block listening on port 8080:

Remember to restart nginx after making this change.

Whichever web server you use, remember to open port 8080 to local traffic (and you probably want to deny anything not local). For example, if using iptables, add -s 192.168.0.0/16 -p tcp —dport 8080 -j ACCEPT to your ruleset (adjust for your LAN subnet if necessary).

Overlay mount of read-only cache

It is possible to use one machine on a local network as a read-only package cache by overlay mounting its /var/cache/pacman/pkg directory. Such a configuration is advantageous if this server has installed on it a reasonably comprehensive selection of up-to-date packages which are also used by other boxes. This is useful for maintaining a number of machines at the end of a low bandwidth upstream connection.

As an example, to use this method:

Note concerning overlay: The working directory must be an empty directory on the same mounted device as the upper directory.

After this, run pacman using the option —cachedir /tmp/pacman_pkg , e.g.:

Distributed read-only cache

There are Arch-specific tools for automatically discovering other computers on your network offering a package cache. Try pacredir , pacserve, pkgdistcache AUR , or paclan AUR . pkgdistcache uses Avahi instead of plain UDP which may work better in certain home networks that route instead of bridge between WiFi and Ethernet.

Historically, there was PkgD and multipkg, but they are no longer maintained.

Read-write cache

In order to share packages between multiple computers, simply share /var/cache/pacman/ using any network-based mount protocol. This section shows how to use shfs or SSHFS to share a package cache plus the related library-directories between multiple computers on the same local network. Keep in mind that a network shared cache can be slow depending on the file-system choice, among other factors.

First, install any network-supporting filesystem packages: shfs-utils , sshfs , curlftpfs , samba or nfs-utils .

Then, to share the actual packages, mount /var/cache/pacman/pkg from the server to /var/cache/pacman/pkg on every client machine.

two-way with rsync

Another approach in a local environment is rsync. Choose a server for caching and enable the Rsync#rsync daemon. On clients synchronize two-way with this share via the rsync protocol. Filenames that contain colons are no problem for the rsync protocol.

Draft example for a client, using uname -m within the share name ensures an architecture-dependent sync:

Dynamic reverse proxy cache using nginx

nginx can be used to proxy package requests to official upstream mirrors and cache the results to the local disk. All subsequent requests for that package will be served directly from the local cache, minimizing the amount of internet traffic needed to update a large number of computers.

In this example, the cache server will run at http://cache.domain.example:8080/ and store the packages in /srv/http/pacman-cache/ .

Install nginx on the computer that is going to host the cache. Create the directory for the cache and adjust the permissions so nginx can write files to it:

Use the nginx pacman cache config as a starting point for /etc/nginx/nginx.conf . Check that the resolver directive works for your needs. In the upstream server blocks, configure the proxy_pass directives with addresses of official mirrors, see examples in the config file about the expected format. Once you are satisfied with the configuration file start and enable nginx.

In order to use the cache each Arch Linux computer (including the one hosting the cache) must have the following line at the top of the mirrorlist file:

Pacoloco proxy cache server

Pacoloco is an easy-to-use proxy cache server for pacman repositories. It also allows automatic prefetching of the cached packages.

It can be installed as pacoloco . Open the configuration file and add pacman mirrors:

Restart pacoloco.service and the proxy repository will be available at http://myserver:9129/repo/mycopy .

Flexo proxy cache server

Flexo is yet another proxy cache server for pacman repositories. Flexo is available as flexo-git AUR . Once installed, start the flexo.service unit.

Flexo runs on port 7878 by default. Enter Server = http://myserver:7878/$repo/os/$arch to the top of your /etc/pacman.d/mirrorlist so that pacman downloads packages via Flexo.

Synchronize pacman package cache using synchronization programs

Use Syncthing or Resilio Sync to synchronize the pacman cache folders (i.e. /var/cache/pacman/pkg ).

Preventing unwanted cache purges

By default, pacman -Sc removes package tarballs from the cache that correspond to packages that are not installed on the machine the command was issued on. Because pacman cannot predict what packages are installed on all machines that share the cache, it will end up deleting files that should not be.

To clean up the cache so that only outdated tarballs are deleted, add this entry in the [options] section of /etc/pacman.conf :

Recreate a package from the file system

To recreate a package from the file system, use fakepkg AUR . Files from the system are taken as they are, hence any modifications will be present in the assembled package. Distributing the recreated package is therefore discouraged; see ABS and Arch Linux Archive for alternatives.

List of installed packages

Keeping a list of all the explicitly installed packages can be useful, to backup a system for example or speed up installation on a new system:

To keep an up-to-date list of explicitly installed packages (e.g. in combination with a versioned /etc/ ), you can set up a hook. Example:

Install packages from a list

To install packages from a previously saved list of packages, while not reinstalling previously installed packages that are already up-to-date, run:

However, it is likely foreign packages such as from the AUR or installed locally are present in the list. To filter out from the list the foreign packages, the previous command line can be enriched as follows:

Eventually, to make sure the installed packages of your system match the list and remove all the packages that are not mentioned in it:

Listing all changed files from packages

If you are suspecting file corruption (e.g. by software/hardware failure), but are unsure if files were corrupted, you might want to compare with the hash sums in the packages. This can be done with pacutils :

Reinstalling all packages

To reinstall all native packages, use:

Foreign (AUR) packages must be reinstalled separately; you can list them with pacman -Qqm .

Pacman preserves the installation reason by default.

Restore pacman’s local database

Recovering a USB key from existing install

If you have Arch installed on a USB key and manage to mess it up (e.g. removing it while it is still being written to), then it is possible to re-install all the packages and hopefully get it back up and working again (assuming USB key is mounted in /newarch )

Viewing a single file inside a .pkg file

For example, if you want to see the contents of /etc/systemd/logind.conf supplied within the systemd package:

Or you can use vim to browse the archive:

Find applications that use libraries from older packages

Even if you installed a package the existing long-running programs (like daemons and servers) still keep using code from old package libraries. And it is a bad idea to let these programs running if the old library contains a security bug.

Here is a way how to find all the programs that use old packages code:

It will print running program name and old library that was removed or replaced with newer content.

Installing only content in required languages

Many packages attempt to install documentation and translations in several languages. Some programs are designed to remove such unnecessary files, such as localepurge AUR , which runs after a package is installed to delete the unneeded locale files. A more direct approach is provided through the NoExtract directive in pacman.conf , which prevent these files from ever being installed.

The example below installs English (US) files, or none at all:

Performance

Download speeds

When downloading packages pacman uses the mirrors in the order they are in /etc/pacman.d/mirrorlist . The mirror which is at the top of the list by default however may not be the fastest for you. To select a faster mirror, see Mirrors.

Pacman’s speed in downloading packages can also be improved by using a different application to download packages, instead of pacman‘s built-in file downloader, or by enabling parallel downloads.

In all cases, make sure you have the latest pacman before doing any modifications.

Powerpill

Powerpill is a pacman wrapper that uses parallel and segmented downloading to try to speed up downloads for pacman.

This is also very handy if you need more powerful proxy settings than pacman‘s built-in capabilities.

To use wget , first install the wget package then modify /etc/pacman.conf by uncommenting the following line in the [options] section:

Instead of uncommenting the wget parameters in /etc/pacman.conf , you can also modify the wget configuration file directly (the system-wide file is /etc/wgetrc , per user files are $HOME/.wgetrc ).

aria2

aria2 is a lightweight download utility with support for resumable and segmented HTTP/HTTPS and FTP downloads. aria2 allows for multiple and simultaneous HTTP/HTTPS and FTP connections to an Arch mirror, which should result in an increase in download speeds for both file and package retrieval.

Install aria2 , then edit /etc/pacman.conf by adding the following line to the [options] section:

See aria2c(1) § OPTIONS for used aria2c options.

• -d, —dir : The directory to store the downloaded file(s) as specified by pacman.
• -o, —out : The output file name(s) of the downloaded file(s).
• %o : Variable which represents the local filename(s) as specified by pacman.
• %u : Variable which represents the download URL as specified by pacman.

Other applications

There are other downloading applications that you can use with pacman. Here they are, and their associated XferCommand settings:

• snarf : XferCommand = /usr/bin/snarf -N %u
• lftp : XferCommand = /usr/bin/lftp -c pget %u
• axel : XferCommand = /usr/bin/axel -n 2 -v -a -o %o %u
• hget : XferCommand = /usr/bin/hget %u -n 2 -skip-tls false (please read the documentation on the Github project page for more info)
• saldl : XferCommand = /usr/bin/saldl -c6 -l4 -s2m -o %o %u (please read the documentation on the project page for more info)

Источник