How to install from aur
How to install from aur
How to install from aur
Archlinux User Repository (AUR). If you are looking for a software but not available in the official repository. You can still search the software package on the «archlinux user repository» site. AUR is a community-driven repository for Arch users. It contains package descriptions/PKGBUILD that allow you to compile a package from source with makepkg then install it through pacman.
Installing software / packages from AUR (Arch User Repository)
1. Download Software Package in AUR
Please search for the AUR package that you want. Then click on the package, then see the box on the right.
Then select «Download snapshot». Then the tar.gz package will be downloaded. Open the downloaded file using the terminal / console
2. Extract the packages
3. Build packages
The packages will be build
4. Install the packages
Packages will be installed
AUR Download with wget.
Here’s for the example of installation, see below «installing xarchiver»
Wait until package is created, at the end must be like this.
Arch User Repository (Русский)
Пользовательский репозиторий Arch (Arch User Repository, AUR) — поддерживаемое сообществом хранилище программ для пользователей Arch. Содержит описания пакетов (файлы PKGBUILD), которые позволяют скомпилировать пакет из исходников утилитой makepkg и затем установить его с помощью pacman. AUR был создан с целью организации совместного доступа к новым пакетам, которые были созданы сообществом, а также чтобы ускорить добавление популярных пакетов в репозиторий community. В статье описано, как получить доступ к AUR и как с ним работать.
Многие пакеты, в настоящее время находящиеся в официальных репозиториях, когда-то начинали свой путь в AUR. В AUR пользователи могут добавлять собственные сборки пакетов ( PKGBUILD и другие необходимые файлы). Сообществу предоставлена возможность голосовать за понравившиеся пакеты. Если пакет стал популярным, распространяется под подходящей лицензией и собирается без излишних сложностей, то он может быть перенесён в репозиторий community (доступный напрямую с помощью pacman и ABS).
Contents
Приступая к работе
Искать и скачивать файлы PKGBUILD можно через веб-интерфейс AUR. Эти файлы позволяют собрать устанавливаемый пакет утилитой makepkg и установить его в систему с помощью pacman.
Получить доступ к AUR можно и через SSH: команда ssh aur@aur.archlinux.org help выведет список доступных команд.
История
Позднее некоторым участникам сообщества было разрешено содержать собственные репозитории с общим доступом. Так появились репозитории доверенных пользователей (Trusted User Repositories). AUR был создан как развитие этой идеи, чтобы сделать систему более гибкой и удобной. AUR-мэйнтейнеры до сих пор часто упоминаются как доверенные пользователи (Trusted Users, TU).
Git-репозитории с пакетами AUR3
Архив AUR на GitHub содержит все пакеты AUR3 на момент миграции. Также существует репозиторий aur3-mirror с аналогичным содержанием.
Установка и обновление пакетов
Установка пакетов из AUR относительно проста:
Подготовка
Выберите подходящий каталог сборки. Каталог сборки — это просто место, в котором пакет будет «собран». Им может быть любой каталог в системе. В примерах ниже в качестве каталога сборки выбран
Получение файлов
Найдите пакет в AUR. Это можно сделать поиском на главной странице AUR (текстовое поле вверху). После перехода по одной из ссылок из списка результатов откроется страница информации о выбранном пакете. Прочтите описание, убедитесь, что это то, что вы искали; обратите внимание на дату последнего обновления пакета и прочтите комментарии.
Существует несколько способов получить необходимые файлы пакета:
Получение открытого ключа PGP (при необходимости)
Проверьте массив source в файле PKGBUILD на предмет наличия в нём файла подписи (суффикс .sig или .asc), и, если таковой присутствует, получите любой открытый ключ из массива validpgpkeys. Подробнее см. makepkg#Проверка цифровых подписей.
Сборка пакета
Перейдите в каталог, содержащий PKGBUILD пакета:
Просмотрите содержимое всех предоставленных файлов. Например, для просмотра PKGBUILD с помощью less выполните:
Соберите пакет. После ручной проверки целостности файлов запустите makepkg от имени обычного пользователя. Некоторые полезные флаги:
Установка пакета
После сборки можно установить пакет с помощью pacman:
Обновление пакета
В каталоге с PKGBUILD пакета сначала обновите файлы командой
после чего повторите процесс сборки и установки, описанный выше.
Обратная связь
Комментарии к пакету
Веб-интерфейс AUR имеет возможность комментирования, благодаря которой пользователи могут сообщить мэйнтейнеру PKGBUILD о предложениях и улучшениях.
Python-Markdown предоставляет базовый Markdown-синтаксис для форматирования комментариев.
Голосование
Одним из самых простых действий для всех пользователей Arch Linux является обзор AUR и голосование за понравившиеся пакеты.
Каждый пакет может быть принят кем-нибудь из доверенных пользователей в репозиторий community. Количество голосов — один из важных критериев, поэтому в интересах пользователей активное голосование за пакеты.
Кроме того, если настроена ssh-аутентификация, можно проголосовать из командной строки с использованием ssh-ключа. Это означает, что не придётся сохранять или вводить пароль от AUR.
Устаревшие пакеты
Используйте Пометить пакет как устаревший для установки соответствующего флага. Укажите причину, по которой вы сочли пакет устаревшим, лучше всего — указав ссылку на объявление о релизе или его tarball.
Также можно попробовать связаться с сопроводителем по email. Если ответа не последует в течение двух недель, можно отправить запрос Сделать сиротой для данного пакета. Смотрите AUR submission guidelines (Русский)#Запросы для дополнительной информации.
Отладка процесса сборки пакета
Если у вас проблемы со сборкой пакета, первым делом почитайте PKGBUILD и комментарии на странице AUR.
Вполне может оказаться, что PKGBUILD сломан для всех. Если вы не можете разобраться сами, сообщите сопроводителю пакета (например, текст ошибки в комментарии на странице AUR). Также можно поискать помощь на AUR Issues, Discussion & PKGBUILD Requests forum.
Отправка пакетов
При помощи AUR пользователи могут распространять свои файлы PKGBUILD. Инструкции и правила публикации описаны в статье AUR submission guidelines (Русский).
Перевод веб-интерфейса
Информацию о создании и поддержке перевода веб-интерфейса AUR смотрите в файле i18n.txt в дереве исходных текстов AUR.
Часто задаваемые вопросы
Какие типы пакетов разрешены в AUR?
Пакеты AUR — это просто «скрипты сборки» исполняемых файлов для последующей упаковки полученных бинарных файлов в пакет и установки при помощи pacman. Обычно разрешено всё, что удовлетворяет принципам полезности, инструкциям и лицензионным требованиям программного обеспечения. Но в некоторых случаях прямо указано, что запрещено создавать ссылки на скачивание, например, когда контент запрещен к распространению, вы можете использовать лишь само имя файла в качестве исходника. Это означает, что пользователь должен самостоятельно озаботиться в получении таких файлов. Если вы сомневаетесь в правовых аспектах, лучше сначала спросить.
Как я могу голосовать за пакеты в AUR?
Кто такие доверенные пользователи/TU?
Доверенный пользователь (Trusted User, TU) — это пользователь, выбранный для сопровождения AUR и репозитория community. Они поддерживают популярные файлы PKGBUILD в community и работу AUR в целом.
В чем разница между AUR и репозиторием community?
Arch User Repository — это место, где хранятся все файлы PKGBUILD, присланные пользователями. Сами пакеты должны быть собраны вручную при помощи makepkg. Когда файлы PKGBUILD набирают достаточный интерес со стороны сообщества и поддержку доверенных пользователей, они собираются в пакеты, которые перемещаются в репозиторий community (поддерживаемый доверенными пользователями), из которого уже могут напрямую быть установлены при помощи pacman.
Пакет из AUR устарел, что я могу сделать?
Пакет foo из AUR не собирается, когда я запускаю makepkg; что мне делать?
Возможно, вы упускаете что-то тривиальное; смотрите #Отладка процесса сборки пакета.
ОШИБКА: Одна или больше PGP-подписей не могут быть проверены! Что мне делать?
Скорее всего, у вас нет необходимого открытого ключа (ключей) в вашей личной связке ключей для проверки скачанных файлов. Смотрите makepkg (Русский)#Проверка цифровых подписей.
Как создать PKGBUILD?
У меня есть PKGBUILD, который я хочу опубликовать; кто-нибудь может проверить его на наличие ошибок?
Существует несколько каналов, по которым можно отправить свой пакет на проверку; смотрите #Отладка процесса сборки пакета.
Что необходимо для перемещения PKGBUILD в репозиторий community?
Обычно необходимо как минимум 10 голосов для того, чтобы пакет мог быть перемещен в community. Однако, если доверенный пользователь захочет поддерживать пакет, он скорее всего сделает это сразу.
Получение пакетом минимально необходимого количества голосов — не единственное требование: у кого-либо из доверенных пользователей должно появиться желание поддерживать этот пакет. Доверенные пользователи не обязаны перемещать пакет в репозиторий community, даже если он имеет тысячи голосов.
В большинстве случаев очень популярные пакеты остаются в AUR по одной или нескольким из следующих причин:
Как ускорить повторную сборку?
В чём разница между пакетами foo и foo-git?
Почему пакет пропал из AUR?
Возможно, пакет был принят доверенным пользователем и теперь находится в репозитории community.
Пакет мог быть удалён, если он не удовлетворял правилам отправки пакетов. Для уточнения причины удаления смотрите архив aur-requests.
Если пакет присутствовал в AUR3, не обязательно, что он перешёл в AUR4. Вы можете попробовать найти его в репозитории git для пакетов AUR3.
Как узнать, пропал ли из AUR какой-либо из установленных мной пакетов?
Самый простой способ — проверить HTTP-статус страницы пакета AUR:
How to install AUR packages (manually + helpers)
The Arch Linux repositories are one of the most complete in all of Linux. If a program is not available in the official Arch Linux repository, it should be available in the Arch User Repository or AUR. So, this post will teach you how to install AUR packages both manually and with some helping program.
INTRODUCTION
So, if a package is available for Linux, it is unlikely you will not find it in the AUR. Many Arch users say that the AUR is one of the main reasons they use Arch Linux. If you use Arch Linux or you are about to move to Arch Linux, you will have to use the AUR sooner or later. However, installing packages from the AUR seems to be complicated if you have never done it before. But I will try to present the process in the easiest way possible.
In the first part of this post, I will show you how to install AUR packages manually. Then, in the second part, you will learn how to use some AUR helpers that simplify and automate the installation process. There are several helpers available. In the video above, I showed how to install and use Yaourt, and aurman. But both these programs are discontinued now. So, in this post, I will show you how to install and use yay, yet another yogurt. The video tutorial showing yay is at the end of this post.
Before we start I would like to warn you that all AUR packages are user-produced content, so use them at your own risk.
Prerequisites
To install AUR packages, you need to have some building programs on your system to compile a program. You will also need the git program to download the source code of the AUR packages. To install all the required packages, run the following command:
Then, press CTRL+O to save the changes and CTRL+X to exit.
After that, you should be able to install AUR packages without problems.
Manual Installation
To install a program from AUR manually, you need to perform a few steps. Basically, you have to do the following:
1. Find the package in the AUR
On Arch Linux website, you need to go to the AUR section. and search for the package you are about to install. For example, I will search for Spotify. Spotify is not in the official repository of Arch Linux because it is proprietary software.
Then, you will see all the information about the program on the next screen. To install an AUR package, you will need to copy the link in Git Clone URL.
2. Clone the repository
3. Check the PKGBUILD file.
4. Compile and install the program.
After that, you can start compiling it by running this command in the program directory:
Depending on the package, it can take quite some time. Next, you have to type your password to install the program.
Now, the program is installed and you can open the program from the main menu.
This way you can install any program from the AUR. As you can see, the process is quite simple, it all comes down to cloning the repository, accessing the folder, verifying the PKGBUILD file and finally, starting the installation.
Install AUR Packages using a helper
There are several AUR helpers available. You can see the full list at this page of Arch Linux Wiki. The installation procedure for these helpers is the same as manual installation from the AUR shown above. I will show how to install yay. It is recommended by the developer of aurman, which I used before, and it is also a recommended helper on Manjaro website. I also liked it after I tested it.
To start installing it, find the git URL of yay in the AUR webpage and clone the repository:
Now, enter the downloaded folder, build and install the program.
Now, yay is available for use. For example, to search for a program in the AUR, use this command:
Finally, to upgrade all the packages, use this command.
As you can see from these commands yay uses the same syntax as in pacman. You can discover all available options of yay with the man command:
I hope you will enjoy using yay.
CONCLUSION
The AUR is a very large source of packages for Arch Linux. It should satisfy the needs of any Linux user. If you were unsure how to use the AUR, I hope you are more confident now as you know how to install AUR packages either manually or with some a helper program such as yay.
Arch User Repository
The Arch User Repository (AUR) is a community-driven repository for Arch users. It contains package descriptions (PKGBUILDs) that allow you to compile a package from source with makepkg and then install it via pacman. The AUR was created to organize and share new packages from the community and to help expedite popular packages’ inclusion into the community repository. This document explains how users can access and utilize the AUR.
A good number of new packages that enter the official repositories start in the AUR. In the AUR, users are able to contribute their own package builds ( PKGBUILD and related files). The AUR community has the ability to vote for packages in the AUR. If a package becomes popular enough — provided it has a compatible license and good packaging technique — it may be entered into the community repository (directly accessible by pacman or abs).
Contents
Getting started
Users can search and download PKGBUILDs from the AUR Web Interface. These PKGBUILD s can be built into installable packages using makepkg, then installed using pacman.
It is also possible to interact with the AUR through SSH: type ssh aur@aur.archlinux.org help for a list of available commands.
History
Then the Trusted User Repositories were born. Certain individuals in the community were allowed to host their own repositories for anyone to use. The AUR expanded on this basis, with the aim of making it both more flexible and more usable. In fact, the AUR maintainers are still referred to as TUs (Trusted Users).
Between 2015-06-08 and 2015-08-08 the AUR transitioned from version 3.5.1 to 4.0.0, introducing the use of Git repositories for publishing the PKGBUILD s. Existing packages were dropped unless manually migrated to the new infrastructure by their maintainers.
Git repositories for AUR3 packages
The AUR Archive on GitHub has a repository for every package that was in AUR 3 at the time of the migration. Alternatively, there is the aur3-mirror repository which provides the same.
Installing and upgrading packages
Installing packages from the AUR is a relatively simple process. Essentially:
Prerequisites
First ensure that the necessary tools are installed by installing the base-devel group in full which includes make and other tools needed for compiling from source.
Next choose an appropriate build directory. A build directory is simply a directory where the package will be made or «built» and can be any directory. The examples in the following sections will use
/builds as the build directory.
Acquire build files
Locate the package in the AUR. This is done using the search field at the top of the AUR home page. Clicking the application’s name in the search list brings up an information page on the package. Read through the description to confirm that this is the desired package, note when the package was last updated, and read any comments.
There are several methods for acquiring the build files for a package:
Acquire a PGP public key if needed
Check if a signature file in the form of .sig or .asc is part of the PKGBUILD source array, if that is the case, then acquire one of the public keys listed in the PKGBUILD validpgpkeys array. Refer to makepkg#Signature checking for more information.
Build the package
Change directories to the directory containing the package’s PKGBUILD.
View the contents of all provided files. For example, to use the pager less to view PKGBUILD do:
Make the package. After manually confirming the contents of the files, run makepkg as a normal user. Some helpful flags:
Install the package
The package can now be installed with pacman:
Upgrading packages
In the directory containing the package’s PKGBUILD you must first update the files and changes by using the command
then follow the previous build and install instructions.
Account status
Suspension
When editing a user as a Trusted User, the Suspended field can be set, which suspends the target user. When a user is suspended, they cannot:
Inactivity
When editing your own account or another as a Trusted User, the Inactive field can be set. Inactive accounts are used for two reasons:
Feedback
Commenting on packages
The AUR Web Interface has a comments facility that allows users to provide suggestions and feedback on improvements to the PKGBUILD contributor.
Python-Markdown provides basic Markdown syntax to format comments.
Voting for packages
One of the easiest activities for all Arch users is to browse the AUR and vote for their favourite packages using the online interface. All packages are eligible for adoption by a TU for inclusion in the community repository, and the vote count is one of the considerations in that process; it is in everyone’s interest to vote!
Alternatively, if you have set up ssh authentication, you can directly vote from the command line using your ssh key. This means that you will not need to save or type in your AUR password.
Flagging packages out-of-date
First, you should flag the package out-of-date indicating details on why the package is outdated, preferably including links to the release announcement or the new release tarball.
You should also try to reach out to the maintainer directly by email. If there is no response from the maintainer after two weeks, you can file an orphan request. See AUR submission guidelines#Requests for details.
Debugging the package build process
If you are having trouble building a package, first read its PKGBUILD and the comments on its AUR page.
It is possible that a PKGBUILD is broken for everyone. If you cannot figure it out on your own, report it to the maintainer (e.g. by posting the errors you are getting in the comments on the AUR page). You may also seek help in the AUR Issues, Discussion & PKGBUILD Requests forum.
Submitting packages
Users can share PKGBUILDs using the Arch User Repository. See AUR submission guidelines for details.
Web interface translation
See i18n.txt in the AUR source tree for information about creating and maintaining translation of the AUR Web Interface.
What kind of packages are permitted on the AUR?
The packages on the AUR are merely «build scripts», i.e. recipes to build binaries for pacman. For most cases, everything is permitted, subject to usefulness and scope guidelines, as long as you are in compliance with the licensing terms of the content. For other cases, where it is mentioned that «you may not link» to downloads, i.e. contents that are not redistributable, you may only use the file name itself as the source. This means and requires that users already have the restricted source in the build directory prior to building the package. When in doubt, ask.
How can I vote for packages in the AUR?
What is a Trusted User / TU?
A Trusted User, in short TU, is a person who is chosen to oversee AUR and the community repository. They are the ones who maintain popular PKGBUILDs in community, and overall keep the AUR running.
What is the difference between the Arch User Repository and the community repository?
The Arch User Repository is where all PKGBUILDs that users submit are stored, and must be built manually with makepkg. When PKGBUILD s receive enough community interest and the support of a TU, they are moved into the community repository (maintained by the TUs), where the binary packages can be installed with pacman.
Foo in the AUR is outdated; what should I do?
In the meantime, you can try updating the package yourself by editing the PKGBUILD locally. Sometimes, updates do not require changes to the build or package process, in which case simply updating the pkgver or source array is sufficient.
Foo in the AUR does not compile when I run makepkg; what should I do?
You are probably missing something trivial, see #Debugging the package build process.
ERROR: One or more PGP signatures could not be verified!; what should I do?
Most likely you do not have the required public key(s) in your personal keyring to verify downloaded files. See Makepkg#Signature checking for details.
How do I create a PKGBUILD?
I have a PKGBUILD I would like to submit; can someone check it to see if there are any errors?
There are several channels available to submit your package for review; see #Debugging the package build process.
How to get a PKGBUILD into the community repository?
Usually, at least 10 votes are required for something to move into community. However, if a TU wants to support a package, it will often be found in the repository.
Reaching the required minimum of votes is not the only requirement, there has to be a TU willing to maintain the package. TUs are not required to move a package into the community repository even if it has thousands of votes.
Usually when a very popular package stays in the AUR it is because:
How can I speed up repeated build processes?
What is the difference between foo and foo-git packages?
Why has foo disappeared from the AUR?
It is possible the package has been adopted by a TU and is now in the community repository.
Packages may be deleted if they did not fulfill the rules of submission. See the aur-requests archives for the reason for deletion.
If the package used to exist in AUR3, it might not have been migrated to AUR4. See the #Git repositories for AUR3 packages where these are preserved.
How do I find out if any of my installed packages disappeared from AUR?
The simplest way is to check the HTTP status of the package’s AUR page:
Arch User Repository
The Arch User Repository (AUR) is a community-driven repository for Arch users. It contains package descriptions (PKGBUILDs) that allow you to compile a package from source with makepkg and then install it via pacman. The AUR was created to organize and share new packages from the community and to help expedite popular packages’ inclusion into the community repository. This document explains how users can access and utilize the AUR.
A good number of new packages that enter the official repositories start in the AUR. In the AUR, users are able to contribute their own package builds ( PKGBUILD and related files). The AUR community has the ability to vote for packages in the AUR. If a package becomes popular enough — provided it has a compatible license and good packaging technique — it may be entered into the community repository (directly accessible by pacman or abs).
Contents
Getting started
Users can search and download PKGBUILDs from the AUR Web Interface. These PKGBUILD s can be built into installable packages using makepkg, then installed using pacman.
It is also possible to interact with the AUR through SSH: type ssh aur@aur.archlinux.org help for a list of available commands.
History
Then the Trusted User Repositories were born. Certain individuals in the community were allowed to host their own repositories for anyone to use. The AUR expanded on this basis, with the aim of making it both more flexible and more usable. In fact, the AUR maintainers are still referred to as TUs (Trusted Users).
Between 2015-06-08 and 2015-08-08 the AUR transitioned from version 3.5.1 to 4.0.0, introducing the use of Git repositories for publishing the PKGBUILD s. Existing packages were dropped unless manually migrated to the new infrastructure by their maintainers.
Git repositories for AUR3 packages
The AUR Archive on GitHub has a repository for every package that was in AUR 3 at the time of the migration. Alternatively, there is the aur3-mirror repository which provides the same.
Installing and upgrading packages
Installing packages from the AUR is a relatively simple process. Essentially:
Prerequisites
First ensure that the necessary tools are installed by installing the base-devel group in full which includes make and other tools needed for compiling from source.
Next choose an appropriate build directory. A build directory is simply a directory where the package will be made or «built» and can be any directory. The examples in the following sections will use
/builds as the build directory.
Acquire build files
Locate the package in the AUR. This is done using the search field at the top of the AUR home page. Clicking the application’s name in the search list brings up an information page on the package. Read through the description to confirm that this is the desired package, note when the package was last updated, and read any comments.
There are several methods for acquiring the build files for a package:
Acquire a PGP public key if needed
Check if a signature file in the form of .sig or .asc is part of the PKGBUILD source array, if that is the case, then acquire one of the public keys listed in the PKGBUILD validpgpkeys array. Refer to makepkg#Signature checking for more information.
Build the package
Change directories to the directory containing the package’s PKGBUILD.
View the contents of all provided files. For example, to use the pager less to view PKGBUILD do:
Make the package. After manually confirming the contents of the files, run makepkg as a normal user. Some helpful flags:
Install the package
The package can now be installed with pacman:
Upgrading packages
In the directory containing the package’s PKGBUILD you must first update the files and changes by using the command
then follow the previous build and install instructions.
Account status
Suspension
When editing a user as a Trusted User, the Suspended field can be set, which suspends the target user. When a user is suspended, they cannot:
Inactivity
When editing your own account or another as a Trusted User, the Inactive field can be set. Inactive accounts are used for two reasons:
Feedback
Commenting on packages
The AUR Web Interface has a comments facility that allows users to provide suggestions and feedback on improvements to the PKGBUILD contributor.
Python-Markdown provides basic Markdown syntax to format comments.
Voting for packages
One of the easiest activities for all Arch users is to browse the AUR and vote for their favourite packages using the online interface. All packages are eligible for adoption by a TU for inclusion in the community repository, and the vote count is one of the considerations in that process; it is in everyone’s interest to vote!
Alternatively, if you have set up ssh authentication, you can directly vote from the command line using your ssh key. This means that you will not need to save or type in your AUR password.
Flagging packages out-of-date
First, you should flag the package out-of-date indicating details on why the package is outdated, preferably including links to the release announcement or the new release tarball.
You should also try to reach out to the maintainer directly by email. If there is no response from the maintainer after two weeks, you can file an orphan request. See AUR submission guidelines#Requests for details.
Debugging the package build process
If you are having trouble building a package, first read its PKGBUILD and the comments on its AUR page.
It is possible that a PKGBUILD is broken for everyone. If you cannot figure it out on your own, report it to the maintainer (e.g. by posting the errors you are getting in the comments on the AUR page). You may also seek help in the AUR Issues, Discussion & PKGBUILD Requests forum.
Submitting packages
Users can share PKGBUILDs using the Arch User Repository. See AUR submission guidelines for details.
Web interface translation
See i18n.txt in the AUR source tree for information about creating and maintaining translation of the AUR Web Interface.
What kind of packages are permitted on the AUR?
The packages on the AUR are merely «build scripts», i.e. recipes to build binaries for pacman. For most cases, everything is permitted, subject to usefulness and scope guidelines, as long as you are in compliance with the licensing terms of the content. For other cases, where it is mentioned that «you may not link» to downloads, i.e. contents that are not redistributable, you may only use the file name itself as the source. This means and requires that users already have the restricted source in the build directory prior to building the package. When in doubt, ask.
How can I vote for packages in the AUR?
What is a Trusted User / TU?
A Trusted User, in short TU, is a person who is chosen to oversee AUR and the community repository. They are the ones who maintain popular PKGBUILDs in community, and overall keep the AUR running.
What is the difference between the Arch User Repository and the community repository?
The Arch User Repository is where all PKGBUILDs that users submit are stored, and must be built manually with makepkg. When PKGBUILD s receive enough community interest and the support of a TU, they are moved into the community repository (maintained by the TUs), where the binary packages can be installed with pacman.
Foo in the AUR is outdated; what should I do?
In the meantime, you can try updating the package yourself by editing the PKGBUILD locally. Sometimes, updates do not require changes to the build or package process, in which case simply updating the pkgver or source array is sufficient.
Foo in the AUR does not compile when I run makepkg; what should I do?
You are probably missing something trivial, see #Debugging the package build process.
ERROR: One or more PGP signatures could not be verified!; what should I do?
Most likely you do not have the required public key(s) in your personal keyring to verify downloaded files. See Makepkg#Signature checking for details.
How do I create a PKGBUILD?
I have a PKGBUILD I would like to submit; can someone check it to see if there are any errors?
There are several channels available to submit your package for review; see #Debugging the package build process.
How to get a PKGBUILD into the community repository?
Usually, at least 10 votes are required for something to move into community. However, if a TU wants to support a package, it will often be found in the repository.
Reaching the required minimum of votes is not the only requirement, there has to be a TU willing to maintain the package. TUs are not required to move a package into the community repository even if it has thousands of votes.
Usually when a very popular package stays in the AUR it is because:
How can I speed up repeated build processes?
What is the difference between foo and foo-git packages?
Why has foo disappeared from the AUR?
It is possible the package has been adopted by a TU and is now in the community repository.
Packages may be deleted if they did not fulfill the rules of submission. See the aur-requests archives for the reason for deletion.
If the package used to exist in AUR3, it might not have been migrated to AUR4. See the #Git repositories for AUR3 packages where these are preserved.
How do I find out if any of my installed packages disappeared from AUR?
The simplest way is to check the HTTP status of the package’s AUR page: