Arch_User_Repository

Arch User Repository (AUR for short) is an informal repository run by the community. Instead of a binary package, it is a set of scripts that describe how to build (PKGBUILD), and is often described as the "fruits of the user's knowledge".

You can use makepkg to create a package from the source and install it with Pacman. Popular packages may be imported into the official repository "extra" (or "community" prior to the mid-May 2023 repository consolidation).

Caution!!

The AUR package is provided by users and has not been tested by Arch officials.
The packages supported by NJB are as follows.
* AUR-derived packages in the UVE's repository
* Packages present in "Chaotic AUR"

Let's Try

Packages can be searched and downloaded via the web interface provided by the Arch official, and can also be built using "makepkg" and installed into the environment using Pacman.

Preparation

Make sure you have the base-devel^core meta-package installed (UVE includes it standard).

Get Build File

You can find the package you want on the AUR page.

The build file can be obtained in the following way:

Clone the Git repository of the package (recommended)

The advantage is that you can update the package with "git pull".

git clone https://aur.archlinux.org/pkgname.git

You can also get it from the GitHub mirror.

git clone --branch pkgname --single-branch https://github.com/archlinux/aur.git

Download the snapshot

Also, you can get the tarball from "Download Snapshot" link in "Package Actions" on the right side of the package page, or with the following command:

wget https://aur.archlinux.org/cgit/aur.git/snapshot/pkgname.tar.gz

Since you need to extract it, do so (preferably in the AUR build directory).

tar xvf pkgname.tar.gz

AUR Helper?

AUR helper is a software that automates the use of an AUR, which is particularly useful in these situations.

• Searching for published packages
• Resolving Dependencies Between AUR Packages
• Obtaining and Building the AUR Package
• Retrieving web content such as user comments
• Posting Package to AUR

The most popular ones are yay^chaotic-aur and paru^chaotic-aur, but there are many others. NJB has also developed nako^{univalent-stable} (more details). It is best to use one that has Pacman wrapper functionality.
Others, such as Pamac (pamac-aur^chaotic-aur), can be used as a graphical software center.

F.A.Q

What kind of packages does it have?

For example, the packages each user want to use, the packages that you can't redistribute because of the license, the beta versions of the official packages … and the DKMS-enabled modules and GNOME Shell extensions. It's basically a lawless place.
But calling it a "package" is misleading: it's really just a "build script" - a recipe for creating binaries for Pacman.

What's the difference from the old "community" repository?

It had a binary package. When the community got enough interest, the package was moved to the "community" repository, so you didn't have to create your own package! It was integrated into extra in mid-May 2023, so it will be moved there on and after.

This package is old!

In that case, set the "out-of-date" flag. If possible, it would be helpful if you could include a link to the latest public announcement and a tarball to it in the reason section.
In the meantime, you may want to update the package by editing PKGBUILD in your own environment; if there are no changes to the build process, changes to "pkgver", "source", and checksum are sufficient.

The key authentication failed... (ERROR: One or more PGP signatures could not be verified!)

Most likely, the public key for file verification is not in your personal keyring, so either import the key or temporarily disable it with "--skippgpcheck" when doing makepkg.