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).
- 1 Getting started
- 2 History
- 3 Installing packages
- 4 Feedback
- 5 Sharing and maintaining packages
- 6 Verifying packages
- 7 Web interface translation
- 8 FAQ
- 8.1 What is the AUR?
- 8.2 What kind of packages are permitted on the AUR?
- 8.3 How can I vote for packages in the AUR?
- 8.4 What is a Trusted User / TU?
- 8.5 What is the difference between the Arch User Repository and the community repository?
- 8.6 Foo in the AUR is outdated; what should I do?
- 8.7 Foo in the AUR does not compile when I run makepkg; what should I do?
- 8.8 ERROR: One or more PGP signatures could not be verified!; what should I do?
- 8.9 How do I create a PKGBUILD?
- 8.10 I have a PKGBUILD I would like to submit; can someone check it to see if there are any errors?
- 8.11 How to get a PKGBUILD into the community repository?
- 8.12 How can I speed up repeated build processes?
- 8.13 What is the difference between foo and foo-git packages?
- 8.14 Why has foo disappeared from the AUR?
- 8.15 How do I find out if any of my installed packages disappeared from AUR?
- 8.16 How can I obtain a list of all AUR packages?
- 9 See also
- Ensure the
pacman -S --needed base-devel).
package group is installed in full (
- Glance over the #FAQ for answers to the most common questions.
- You may wish to adjust
/etc/makepkg.confto optimize for your processor prior to building packages from the AUR. A significant improvement in compile times can be realized on systems with multi-core processors by adjusting the MAKEFLAGS variable. Users can also enable hardware-specific optimizations in GCC via the CFLAGS variable. See makepkg for more information.
It is also possible to interact with the AUR through SSH: type
ssh email@example.com help for a list of available commands.
In the beginning, there was
ftp://ftp.archlinux.org/incoming, and people contributed by simply uploading the
PKGBUILD, the needed supplementary files, and the built package itself to the server. The package and associated files remained there until a Package Maintainer saw the program and adopted it.
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
Existing packages were dropped unless manually migrated to the new infrastructure by their maintainers.
Git repositories for AUR3 packages
Installing packages from the AUR is a relatively simple process. Essentially:
- Acquire the build files, including the PKGBUILD and possibly other required files, like systemd units and patches (often not the actual code).
- Verify that the
PKGBUILDand accompanying files are not malicious or untrustworthy.
makepkg -siin the directory where the files are saved. This will download the code, resolve the dependencies with pacman, compile it, package it, and install the package.
First ensure that the necessary tools are installed by installing the group in full which includes 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:
- Option 1: Clone the git repository that is labelled as the "Git Clone URL" in the "Package Details". This is the preferred method.
$ git clone https://aur.archlinux.org/package_name.git
- An advantage of this method is that you can easily get updates to the package via
- Option 2: Download the build files with your web browser by clicking the "Download snapshot" link under "Package Actions" on the right hand side. This will download a compressed file, which must be extracted (preferably in a directory set aside for AUR builds)
$ tar -xvf package_name.tar.gz
- Similarly, you can download a tarball from the terminal (and extract it):
$ curl -L -O https://aur.archlinux.org/cgit/aur.git/snapshot/package_name.tar.gz
Build and install the package
Change directories to the directory containing the package's PKGBUILD.
$ cd package_name
PKGBUILD, any .install files, and any other files in the package's git repository for malicious or dangerous commands. If in doubt, do not build the package, and seek advice on the forums or mailing list. Malicious code has been found in packages before. 
View the contents of all provided files. For example, to use the pager less to view
$ less PKGBUILD
- To view changes since the last git commit you can use
- To view changes since the last commit using vimdiff, do
git difftool @~..@ vimdiff. The advantage of vimdiff is that you view the entire contents of each file along with indicators on what has changed.
Make the package. After manually confirming the contents of the files, run makepkg as a normal user:
$ makepkg -si
--syncdepsautomatically resolves and installs any dependencies with pacman before building. If the package depends on other AUR packages, you will need to manually install them first.
--installinstalls the package if it is built successfully. Alternatively the built package can be installed with
pacman -U package.pkg.tar.xz.
Other useful flags are
--rmdepsremoves build-time dependencies after the build, as they are no longer needed. However these dependencies may need to be reinstalled the next time the package is updated.
--cleancleans up temporary build files after the build, as they are no longer needed. These files are usually needed only when debugging the build process.
The AUR provides various means for users to communicate with package maintainers, provided they have setup an account on the AUR Web Interface.
Commenting on packages
Comments allow users to provide suggestions or respond to updates and maintainers to respond to users or make announcements. The Python-Markdown syntax is supported, which provides basic Markdown syntax for formatting. Maintainers may pin comments by clicking the thumbtack button in their top-right corner.
PKGBUILDs into the comments section; they quickly become obsolete and just end up needlessly taking up lots of space. Instead email those files to the maintainer, or use a pastebin.
Voting for packages
One of the easiest activities for all Arch users is to browse the AUR and vote for their favourite packages. 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!
While logged in, on the AUR page for a package you may click "Vote for this package" under "Package Actions" on the right. It is also possible to vote from the commandline withAUR, AUR, AUR, or AUR.
Alternatively, if you have set up ssh authentication, you can directly vote from the command line using your ssh key and avoid having to save or type in your AUR password.
ssh firstname.lastname@example.org vote <PACKAGE_NAME>
Flagging packages out-of-date
While logged in, on the AUR page for a package you may click "Flag package as out-of-date" under "Package Actions" on the right. You should also leave a comment indicating details as to why the package is outdated, preferably including links to a release announcement or a new release tarball. Also try to reach out to the maintainer directly by email. If there is no response after two weeks, you may file an orphan request.
pkgverchanges, do not flag them as the maintainer will merely unflag the package and ignore you.
Sharing and maintaining packages
Users can share
PKGBUILDs using the Arch User Repository. It does not contain any binary packages but allows users to upload
PKGBUILDs that can be downloaded by others. These
PKGBUILDs are completely unofficial and have not been thoroughly vetted, so they should be used at your own risk.
If you are unsure in any way about a package or the build/submission process even after reading this section twice, submit the PKGBUILD for review.
Rules of submission
When submitting a package to the AUR, observe the following rules:
PKGBUILDs must be in compliance with the licensing terms of the content to be packaged. In 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.
PKGBUILDs must not duplicate applications in any of the official repositories. Check the official package database; if the package exists, do not submit a duplicate. If the official package is out-of-date, flag it as such. If the official package is broken, or lacking a standard feature, please file a bug report.
- The only exception to this is for packages with extra features enabled and/or patches in comparison to the official ones, in which case
pkgbaseshould be different to express that. For example, a package for GNU screen containing the sidebar patch could be named
screen-sidebar. Additionally the
provides=('screen')array should be used in order to avoid conflicts with the official package.
- Check the AUR if the package already exists. If it is currently maintained, changes can be submitted in a comment for the maintainer's attention. If it is unmaintained or the maintainer is unresponsive, the package can be adopted and updated as required. Do not create duplicate packages.
- Make sure the package you want to upload is useful. Will anyone else want to use this package? Is it extremely specialized? If more than a few people would find this package useful, it is appropriate for submission.
- The AUR and official repositories are intended for packages which install generally software and software-related content, including one or more of the following: executable(s); config file(s); online or offline documentation for specific software or the Arch Linux distribution as a whole; media intended to be used directly by software.
- Do not use
replacesin an AUR
PKGBUILDunless the package is to be renamed, for example when Ethereal became Wireshark. If the package is an alternate version of an already existing package, use
providesif that package is required by others). The main difference is: after syncing (-Sy) pacman immediately wants to replace an installed, 'offending' package upon encountering a package with the matching
replacesanywhere in its repositories;
conflicts, on the other hand, is only evaluated when actually installing the package, which is usually the desired behavior because it is less invasive.
- Submitting binaries should be avoided if the sources are available. The AUR should not contain binary tarballs created by makepkg, nor should it contain their filelists. Consult the Nonfree applications package guidelines regarding packages that redistribute prebuilt deliverables and the Java package guidelines regarding packages that redistribute java binaries.
- Please add a comment line to the top of the
PKGBUILDfile which contains information about the current maintainers and previous contributors, respecting the following format. Remember to disguise your email to protect against spam. Additional or unneeded lines are facultative.
- If you are assuming the role of maintainer for an existing
PKGBUILD, add your name to the top like this
# Maintainer: Your Name <address at domain dot tld>
- If there were previous maintainers, put them as contributors. The same applies for the original submitter if this is not you. If you are a co-maintainer, add the names of the other current maintainers as well.
# Maintainer: Your name <address at domain dot tld> # Maintainer: Other maintainer's name <address at domain dot tld> # Contributor: Previous maintainer's name <address at domain dot tld> # Contributor: Original submitter's name <address at domain dot tld>
For write access to the AUR, you need to have an SSH key pair. The content of the public key needs to be copied to your profile in My Account, and the corresponding private key configured for the
aur.archlinux.org host. For example:
Host aur.archlinux.org IdentityFile ~/.ssh/aur User aur
You should create a new key pair rather than use an existing one, so that you can selectively revoke the keys should something happen:
$ ssh-keygen -f ~/.ssh/aur
Creating package repositories
If you are creating a new package from scratch, establish a local Git repository and an AUR remote by cloning the intended pkgbase. If the package does not yet exist, the following warning is expected:
$ git clone ssh://email@example.com/pkgbase.git
Cloning into 'pkgbase'... warning: You appear to have cloned an empty repository. Checking connectivity... done.
pkgbasematches a deleted package.
If you already have a package, initialize it as a Git repository if it isn't one, and add an AUR remote:
$ git remote add label ssh://firstname.lastname@example.org/pkgbase.git
Then fetch this remote to initialize it in the AUR.
pkgbasematches a deleted package.
Publishing new package content
git config user.name "..."and
git config user.email "...".
To upload or update a package add at least PKGBUILD and .SRCINFO then any new or modified .install files, patches or other local source files; commit with a meaningful commit message, and finally push the changes to the AUR.
$ makepkg --printsrcinfo > .SRCINFO $ git add -f PKGBUILD .SRCINFO $ git commit -m "useful commit message" $ git push
- After modifying a package, except for very minor changes (such as fixing a typo) that would not require re-installation of the package, update its version accordingly.
.SRCINFOafter updating such
PKGBUILDmetadata in order to publish it in the AUR.
.SRCINFOwas not added before your first commit, add it by rebasing with --root or filtering the tree so the AUR will permit your initial push.
- Check for feedback and comments from other users and try to incorporate any improvements they suggest; consider it a learning process!
- Please do not leave a comment containing the version number every time you update the package. This keeps the comment section usable for valuable content mentioned above.
- Please do not just submit and forget about packages! It is the maintainer's job to maintain the package by checking for updates and improving the
- If you do not want to continue to maintain the package for some reason,
disownthe package using the AUR web interface and/or post a message to the AUR Mailing List. If all maintainers of an AUR package disown it, it will become an "orphaned" package.
Deletion, merge, and orphan requests can be created by clicking on the "Submit Request" link under "Package Actions" on the right hand side. This will send a notification email to the current maintainer and to the aur-requests mailing list for discussion. A Trusted User will then either accept or reject the request.
You may request to unlist a
pkgbase from the AUR. A short note explaining the reason for deletion is required, as well as supporting details (like when a package is provided by another package, if you are the maintainer yourself, it is renamed and the original owner agreed, etc).
- It is not sufficient to explain why a package is up for deletion only in its comments because as soon as a TU takes action, the only place where such information can be obtained is the aur-requests mailing list.
- Deletion requests can be rejected, in which case if you are the maintainer you will likely be advised to disown the package to allow adoption by another maintainer.
- After a package is "deleted", its git repository remains available for cloning.
You may request to delete a
pkgbase and transfer its votes and comments to another
pkgbase. The name of the package to merge into is required.
You may request that a
pkgbase be disowned. These requests will be granted after two weeks if the current maintainer did not react.
Promoting packages to the community repository
When AUR packages receive enough community interest and the support of a Trusted User, they may be adopted into the community repository (maintained by the TUs), from which binary packages can be installed using pacman.
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.
Sufficient votes are not the only requirement; there has to be a TU willing to maintain the package. TUs are not required to adopt a package even if it has thousands of votes.
Usually, when a very popular package stays in the AUR it is because:
- Arch Linux already has another version of a package in the repositories.
- Its license prohibits redistribution.
- It helps retrieve user-submitted
PKGBUILDs (AUR helpers).
If you are having trouble building a package, 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.
To avoid problems caused by your particular system configuration, build packages in a clean chroot. If the build process still fails in a clean chroot, the issue is probably with the
See Creating packages#Checking package sanity about using
namcap to debug packages. If you would like to have a
PKGBUILD reviewed, post it on the aur-general mailing list to get feedback from the TUs and fellow AUR members, or the Creating & Modifying Packages forum. You could also seek help in the IRC channel #archlinux-aur on Freenode.
Avoid common pitfalls:
- Ensure your build environment is up-to-date by upgrading before building anything.
- Ensure you have both and groups installed.
- Use the
makepkgto check and install all the dependencies needed before starting the build process.
- Try the default makepkg configuration.
- See Makepkg#Troubleshooting for common issues.
Web interface translation
See i18n.txt in the AUR source tree for information about creating and maintaining translation of the AUR web interface.
What is the AUR?
The AUR (Arch User Repository) is a place where the Arch Linux community can upload PKGBUILDs of applications, libraries, etc., and share them with the entire community. Fellow users can then vote for their favorites to be moved into the community repository to be shared with Arch Linux users in binary form.
What kind of packages are permitted on the AUR?
For most cases, everything is permitted, subject to the #Rules of submission.
How can I vote for packages in the AUR?
See #Voting for packages.
What is a Trusted User / TU?
What is the difference between the Arch User Repository and the community repository?
AUR packages are maintained by community members and provided in source format, while the packages in the community repository are maintained by the Trusted Users and provided in pre-compiled binary format. See #Promoting packages to the community repository for more information.
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
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 #Verifying packages.
ERROR: One or more PGP signatures could not be verified!; what should I do?
How do I create a PKGBUILD?
Be sure to check the AUR to avoid duplicating efforts, then see creating packages.
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 #Verifying packages.
How to get a PKGBUILD into the community repository?
How can I speed up repeated build processes?
What is the difference between foo and foo-git packages?
Many AUR packages come in "stable" release and "unstable" development versions. Development packages usually have a suffix denoting their Version Control System and are not intended for regular use, but may offer new features or bugfixes. Because these packages only download the latest available source when you execute
pkgver() in the AUR does not reflect upstream changes. Likewise, these packages cannot perform an authenticity checksum on any VCS source.
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.
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:
$ comm -23 <(pacman -Qqm | sort) <(curl https://aur.archlinux.org/packages.gz | gzip -cd | sort)
How can I obtain a list of all AUR packages?