Difference between revisions of "Arch User Repository"

From ArchWiki
Jump to navigation Jump to search
(→‎Why has foo disappeared from the AUR?: mention that git repositories for deleted packages remain available, ref. AUR_submission_guidelines#Requests)
 
(41 intermediate revisions by 6 users not shown)
Line 24: Line 24:
 
{{Related|.SRCINFO}}
 
{{Related|.SRCINFO}}
 
{{Related|Aurweb RPC interface}}
 
{{Related|Aurweb RPC interface}}
 +
{{Related|AUR submission guidelines}}
 
{{Related|AUR Trusted User Guidelines}}
 
{{Related|AUR Trusted User Guidelines}}
 
{{Related|Official repositories}}
 
{{Related|Official repositories}}
Line 33: Line 34:
 
The Arch User Repository (AUR) is a community-driven repository for Arch users. It contains package descriptions ([[PKGBUILD]]s) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman#Additional commands|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.
 
The Arch User Repository (AUR) is a community-driven repository for Arch users. It contains package descriptions ([[PKGBUILD]]s) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman#Additional commands|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 ({{ic|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]]).
+
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 ({{ic|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]]).
  
{{Warning|AUR packages are user produced content with no official support. Any use of the provided files is at your own risk.}}
+
{{Warning|AUR packages are user produced content. Any use of the provided files is at your own risk.}}
  
 
== Getting started ==
 
== Getting started ==
  
Users can search and download {{ic|PKGBUILD}}s from the [https://aur.archlinux.org AUR Web Interface]. These {{ic|PKGBUILD}}s can be built into installable packages using ''makepkg'', then installed using ''pacman''.
+
Users can search and download [[PKGBUILD]]s from the [https://aur.archlinux.org AUR Web Interface]. These {{ic|PKGBUILD}}s can be built into installable packages using ''makepkg'', then installed using ''pacman''.
  
 
* Ensure the {{Grp|base-devel}} package group is installed in full ({{ic|pacman -S --needed base-devel}}).
 
* Ensure the {{Grp|base-devel}} package group is installed in full ({{ic|pacman -S --needed base-devel}}).
 
* Glance over the [[#FAQ]] for answers to the most common questions.
 
* Glance over the [[#FAQ]] for answers to the most common questions.
* You may wish to adjust {{ic|/etc/makepkg.conf}} to 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 {{ic|MAKEFLAGS}} variable. Users can also enable hardware-specific optimizations in [[GCC]] via the {{ic|CFLAGS}} variable.  See [[makepkg]] for more information.
+
* You may wish to adjust {{ic|/etc/makepkg.conf}} to 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 {{ic|MAKEFLAGS}} variable. Users can also enable hardware-specific optimizations in [[GCC]] via the {{ic|CFLAGS}} variable.  See [[makepkg]] for more information.
  
 
It is also possible to interact with the AUR through SSH: type {{ic|ssh aur@aur.archlinux.org help}} for a list of available commands.
 
It is also possible to interact with the AUR through SSH: type {{ic|ssh aur@aur.archlinux.org help}} for a list of available commands.
Line 49: Line 50:
 
== History ==
 
== History ==
  
In the beginning, there was {{ic|<nowiki>ftp://ftp.archlinux.org/incoming</nowiki>}}, and people contributed by simply uploading the {{ic|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.
+
In the beginning, there was {{ic|<nowiki>ftp://ftp.archlinux.org/incoming</nowiki>}}, 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).
 
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).
Line 68: Line 69:
 
# Run {{ic|makepkg -si}} in 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.
 
# Run {{ic|makepkg -si}} in 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.
  
{{Note|It is ''your responsibility'' to track AUR package updates; ''pacman'' only tracks [[Pacman#Repositories and mirrors|binary repositories]]. When packages in the official repositories are updated, you will need to rebuild any AUR packages that depend on them.}}
+
{{Note|The AUR is unsupported, so any packages you install are ''your responsibility'' to update, not pacman's. If packages in the official repositories are updated, you will need to rebuild any AUR packages that depend on those libraries.}}
 
 
 
=== Prerequisites ===
 
=== Prerequisites ===
  
 
First ensure that the necessary tools are installed by [[install]]ing the {{grp|base-devel}} group in full which includes {{pkg|make}} and other tools needed for compiling from source.
 
First ensure that the necessary tools are installed by [[install]]ing the {{grp|base-devel}} group in full which includes {{pkg|make}} and other tools needed for compiling from source.
 +
 +
{{Tip|Use the {{ic|--needed}} flag when installing the {{grp|base-devel}} group to skip packages you already have instead of reinstalling them.}}
  
 
{{Note|Packages in the AUR assume that the {{grp|base-devel}} group is installed, i.e. they do not list the group's members as dependencies explicitly.}}
 
{{Note|Packages in the AUR assume that the {{grp|base-devel}} group is installed, i.e. they do not list the group's members as dependencies explicitly.}}
Line 82: Line 84:
 
Locate the package in the AUR. This is done using the search field at the top of the [https://aur.archlinux.org/ 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.
 
Locate the package in the AUR. This is done using the search field at the top of the [https://aur.archlinux.org/ 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:
+
There are several methods for acquiring the build files:
  
* Via [[git]]: This is the preferred method. Clone the repository labelled "Git Clone URL" in the "Package Details" on its AUR page:
+
* Clone the [[git]] repository that is labelled as the "Git Clone URL" in the "Package Details". This is the preferred method.
  
 
  $ git clone <nowiki>https://aur.archlinux.org/</nowiki>''package_name''.git
 
  $ git clone <nowiki>https://aur.archlinux.org/</nowiki>''package_name''.git
  
:{{Note|An advantage of this method is that you can easily get updates to the package via {{ic|git pull}}.}}
+
:An advantage of this method is that you can easily get updates to the package via {{ic|git pull}}.
 +
* 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)
  
* Download a snapshot: Either by clicking the "Download snapshot" link under "Package Actions" on the right hand side of its AUR page, or from the terminal:  
+
$ tar -xvf ''package_name''.tar.gz
 +
* Similarly, you can download a tarball from the terminal (and extract it):
  
 
  $ curl -L -O <nowiki>https://aur.archlinux.org/cgit/aur.git/snapshot/</nowiki>''package_name''.tar.gz
 
  $ curl -L -O <nowiki>https://aur.archlinux.org/cgit/aur.git/snapshot/</nowiki>''package_name''.tar.gz
 
:The snapshot file is compressed, and must be extracted (preferably in a directory set aside for AUR builds):
 
 
$ tar -xvf ''package_name''.tar.gz
 
  
 
=== Build and install the package ===
 
=== Build and install the package ===
Line 130: Line 130:
 
== Feedback ==
 
== Feedback ==
  
The AUR provides various means for users to communicate with package maintainers, provided they have setup an account on the [https://aur.archlinux.org AUR Web Interface].
+
The [https://aur.archlinux.org AUR Web Interface] has a comments facility that allows users to provide suggestions and feedback on improvements to the [[PKGBUILD]] contributor. Avoid pasting patches or {{ic|PKGBUILD}}s 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 even use a [[pastebin]].
  
=== Commenting on 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!
  
Comments allow users to provide suggestions or respond to updates and maintainers to respond to users or make announcements. The [https://python-markdown.github.io/ Python-Markdown] syntax is supported, which provides basic [[Wikipedia:Markdown|Markdown]] syntax for formatting. Maintainers may pin comments by clicking the thumbtack button in their top-right corner.
+
== Submitting packages ==
  
{{Note|
+
Users can share [[PKGBUILD]]s using the Arch User Repository. It does not contain any binary packages but allows users to upload {{ic|PKGBUILD}}s that can be downloaded by others. These {{ic|PKGBUILD}}s are completely unofficial and have not been thoroughly vetted, so they should be used at your own risk. See [[AUR submission guidelines]] for details.
* The markdown implementation has some occasional [https://python-markdown.github.io/#differences differences] with the official [https://daringfireball.net/projects/markdown/syntax syntax rules].
 
* Commit hashes to the [[Git]] repository of the package and references to [[Flyspray]] tickets are converted to links automatically.
 
* Long comments are collapsed and can be expanded on demand.}}
 
  
{{Tip|Avoid pasting patches or {{ic|PKGBUILD}}s 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]].}}
+
== Web interface translation ==
 
 
=== 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 [[#Promoting packages to the community repository|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 with {{AUR|aurvote}}, {{AUR|aurvote-git}}, {{AUR|aur-auto-vote-git}}, or {{AUR|aurvote-utils}}.
 
 
 
Alternatively, if you have set up [[#Authentication|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 aur@aur.archlinux.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|orphan]] request.
 
 
 
{{Note|[[VCS package guidelines|VCS packages]] are not considered out-of-date when the {{ic|''pkgver''}} changes, do not flag them as the maintainer will merely unflag the package and ignore you.}}
 
 
 
== Sharing and maintaining packages ==
 
 
 
{{Note|1=Please see [https://wiki.archlinux.org/index.php?title=Talk:Arch_User_Repository&oldid=484964#Scope_of_the_AUR4_section Talk:Arch User Repository#Scope of the AUR4 section] before making changes to this section.}}
 
 
 
Users can share {{ic|PKGBUILD}}s using the Arch User Repository.  It does not contain any binary packages but allows users to upload {{ic|PKGBUILD}}s that can be downloaded by others. These {{ic|PKGBUILD}}s are completely unofficial and have not been thoroughly vetted, so they should be used at your own risk.
 
 
 
=== Submitting packages ===
 
 
 
{{Warning|Before attempting to submit a package you are expected to familiarize yourself with [[Arch packaging standards]] and all the articles under "Related articles". Verify carefully that what you are uploading is correct. Packages that violate the rules may be deleted without warning.}}
 
 
 
If you are unsure in any way about a package or the build/submission process even after reading this section twice, [[#Verifying packages|submit the PKGBUILD for review]].
 
 
 
==== Rules of submission ====
 
 
 
When submitting a package to the AUR, observe the following rules:
 
 
 
* Submitted {{ic|PKGBUILD}}s 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.
 
 
 
* Submitted {{ic|PKGBUILD}}s must not duplicate applications in any of the [[official repositories]]. Check the [https://www.archlinux.org/packages/ 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 [https://bugs.archlinux.org/ 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 {{ic|''pkgbase''}} should be different to express that. For example, a package for GNU screen containing the sidebar patch could be named {{ic|screen-sidebar}}. Additionally the {{ic|1=provides=('screen')}} array should be used in order to avoid conflicts with the official package.
 
 
 
* Do not create duplicate packages. [[#Getting started|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.
 
 
 
* 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 {{ic|replaces}} unless the package has been renamed or deprecates another, for example when ''Ethereal'' became ''Wireshark''. If the package is an alternate version of an existing package, use {{ic|conflicts}} (and {{ic|provides}} when the offending package has dependents).
 
:{{Note|[[PKGBUILD#replaces|replaces]] forces ''pacman'' to install the replacement package as an upgrade of the offending package, while [[PKGBUILD#conflicts|conflicts]] tells ''pacman'' to remove the offending package only if the conflicting package is to be installed.}}
 
 
 
* 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#Package naming|Nonfree applications package guidelines]] regarding packages that redistribute prebuilt [[Wikipedia:Deliverable|deliverables]] and the [[Java package guidelines#Java_packaging_on_Arch_Linux|Java package guidelines]] regarding packages that redistribute java binaries.
 
 
 
* Add a [http://man7.org/linux/man-pages/man1/bash.1.html#COMMENTS comment line] to the top of the {{ic|PKGBUILD}} file 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 {{ic|PKGBUILD}}, add your name to the top like this:
 
:{{bc|<nowiki>
 
# Maintainer: Your Name <address at domain dot tld>
 
</nowiki>}}
 
:If there were previous maintainers, list 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.
 
:{{bc|<nowiki>
 
# 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>
 
</nowiki>}}
 
 
 
==== Authentication ====
 
 
 
For write access to the AUR, you need to have an [[SSH keys|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 {{ic|aur.archlinux.org}} host. For example:
 
 
 
{{hc|~/.ssh/config|
 
Host aur.archlinux.org
 
  IdentityFile ~/.ssh/aur
 
  User aur}}
 
 
 
You should [[SSH_keys#Generating_an_SSH_key_pair|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
 
 
 
{{Tip|You can add multiple public keys to your profile by separating them with a newline in the input field.}}
 
 
 
==== Creating or adopting package repositories ====
 
 
 
If you are [[Creating_packages|creating a new package]] from scratch, or adopting an orphaned package, establish a local Git repository and an AUR remote by [[Git#Getting_a_Git_repository|cloning]] the intended [[PKGBUILD#pkgbase|pkgbase]]. If the package does not yet exist, the following warning is expected:
 
 
 
{{hc|$ git clone <nowiki>ssh://</nowiki>aur@aur.archlinux.org/''pkgbase''.git|
 
Cloning into &apos;''pkgbase''&apos;...
 
warning: You appear to have cloned an empty repository.
 
Checking connectivity... done.}}
 
 
 
{{Note|The repository will not be empty if {{ic|''pkgbase''}} matches a [[#Deletion|deleted]] package.}}
 
 
 
If you already have a package, [[Git#Getting_a_Git_repository|initialize it]] as a Git repository if it isn't one, and add an AUR remote:
 
 
 
$ git remote add ''label'' <nowiki>ssh://</nowiki>aur@aur.archlinux.org/''pkgbase''.git
 
 
 
Then [[Git#Using remotes|fetch]] this remote to initialize it in the AUR.
 
 
 
{{Note|[https://git-scm.com/docs/git-pull#git-pull---rebasefalsetruemergespreserveinteractive Pull and rebase] to resolve conflicts if {{ic|''pkgbase''}} matches a deleted package.}}
 
 
 
==== Publishing new package content ====
 
 
 
{{Warning|Your commits will be authored with your [[Git#Configuration|global Git name and email address]]. It is very difficult to change commits after pushing them ({{Bug|45425}}). If you want to push to the AUR under different credentials, you can change them per package with {{ic|git config user.name "..."}} and {{ic|git config user.email "..."}}.}}
 
 
 
To upload or update a package [[Git#Staging_changes|add]] ''at least'' [[PKGBUILD]] and [[.SRCINFO]] then any new or modified [[PKGBUILD#install|.install]] files, [[Patching_packages|patches]] or other [[PKGBUILD#source|local source files]]; [[Git#Committing changes|commit]] with a meaningful commit message, and finally [[Git#Push_to_a_repository|push]] the changes to the AUR.
 
 
 
{{Tip|To keep the working directory and commits as clean as possible, create a {{man|5|gitignore}} that excludes all files and force-add files as needed.}}
 
 
 
For example:
 
 
 
$ makepkg --printsrcinfo > .SRCINFO
 
$ git add -f PKGBUILD .SRCINFO
 
$ git commit -m "''useful commit message''"
 
$ git push
 
 
 
{{Note|
 
* 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 [[PKGBUILD#Version|version]] accordingly.
 
* Regenerate {{ic|.SRCINFO}} after updating such {{ic|PKGBUILD}} metadata in order to publish it in the AUR.
 
* If {{ic|.SRCINFO}} was not added before your first commit, add it by [https://git-scm.com/docs/git-rebase#git-rebase---root rebasing with --root] or [https://git-scm.com/docs/git-filter-branch#git-filter-branch---tree-filterltcommandgt filtering the tree] so the AUR will permit your initial push.}}
 
 
 
=== Maintaining packages ===
 
 
 
* Check for feedback and comments from other users and try to incorporate any improvements they suggest; consider it a learning process!
 
* 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.
 
* 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 {{ic|PKGBUILD}}.
 
* Additional maintainers can be added to or removed from a package by clicking "Manage Co-Maintainers" under "Package Actions" on the right of its AUR page and editing the list.
 
* If you do not want to continue to maintain the package for some reason, disown the package by clicking "Disown package" under "Package Actions" on the right of its AUR page and/or post a message to the AUR Mailing List. If all maintainers of an AUR package disown it, it will become an [https://aur.archlinux.org/packages/?SB=n&do_Orphans=Orphans "orphaned"] package.
 
* Orphaned packges can be adopted by clicking on the "Adopt Package" link under "Package Actions" on the right of its AUR page. This will allow you to [[#Publishing_new_package_content|push]] changes to its git repository.
 
 
 
=== Other requests ===
 
  
[[#Deletion|Deletion]], [[#Merge|merge]], and [[#Orphan|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 [https://mailman.archlinux.org/mailman/listinfo/aur-requests aur-requests mailing list] for discussion. A [[Trusted User]] will then either accept or reject the request.  
+
See [https://projects.archlinux.org/aurweb.git/tree/doc/i18n.txt i18n.txt] in the AUR source tree for information about creating and maintaining translation of the [https://aur.archlinux.org AUR Web Interface].
  
==== Deletion ====
+
== Comment syntax ==
  
You may request to ''unlist'' a {{ic|''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).
+
The [https://python-markdown.github.io/ Python-Markdown] syntax is supported in comments.
{{Note|
+
It provides basic [[Wikipedia:Markdown|Markdown]] syntax to format comments. Note this implementation has some occasional [https://python-markdown.github.io/#differences differences] with the official [https://daringfireball.net/projects/markdown/syntax syntax rules]. Commit hashes to the [[Git]] repository of the package and references to [[Flyspray]] tickets are converted to links automatically. Long comments are collapsed and can be expanded on demand.
* 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 [[#Acquire build files|cloning]].}}
 
 
 
==== Merge ====
 
 
 
You may request to delete a {{ic|''pkgbase''}} and transfer its votes and comments to another {{ic|''pkgbase''}}. The name of the package to merge into is required.
 
{{Note|This has nothing to do with 'git merge' or GitLab's merge requests.}}
 
 
 
==== Orphan ====
 
 
 
You may request that a {{ic|''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 [[#Voting on packages|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 {{ic|PKGBUILD}}s ([[AUR helpers]]).
 
 
 
See also [[AUR Trusted User Guidelines#Rules for Packages Entering the .5Bcommunity.5D Repo|Rules for Packages Entering the community Repo]].
 
 
 
== Verifying packages ==
 
 
 
If you are having trouble building a package, read its [[PKGBUILD]] and the comments on its AUR page. It is possible that a {{ic|PKGBUILD}} is broken for everyone. If you cannot figure it out on your own, report it to the maintainer (e.g. by [[#Commenting on packages|posting the errors you are getting in the comments on the AUR page]]). You may also seek help in the [https://bbs.archlinux.org/viewforum.php?id=38 AUR Issues, Discussion & PKGBUILD Requests forum].
 
 
 
* To avoid problems caused by your particular system configuration, build packages in a [[DeveloperWiki:Building in a clean chroot|clean chroot]]. If the build process still fails in a clean chroot, the issue is probably with the {{ic|PKGBUILD}}.
 
 
 
* See [[Creating packages#Checking package sanity]] about using ''namcap'' to debug packages.
 
 
 
* If you would like to have a {{ic|PKGBUILD}} reviewed, post it on the [https://mailman.archlinux.org/mailman/listinfo/aur-general aur-general mailing list] to get feedback from the TUs and fellow AUR members, or the [https://bbs.archlinux.org/viewforum.php?id=4 Creating & Modifying Packages forum]. You could also seek help in the [[IRC channel]] [ircs://chat.freenode.net/archlinux-aur #archlinux-aur] on [https://freenode.net/ Freenode].
 
 
 
Avoid common pitfalls:
 
# Ensure your build environment is up-to-date by [[Pacman#Upgrading_packages|upgrading]] before building anything.
 
# Ensure you have both {{Grp|base}} and {{Grp|base-devel}} groups installed.
 
# Use the {{ic|-s}} option with ''makepkg'' to check and install all the dependencies needed before starting the build process.
 
# Try the default [https://git.archlinux.org/svntogit/packages.git/tree/trunk/makepkg.conf?h=packages/pacman makepkg configuration].
 
# See [[Makepkg#Troubleshooting]] for common issues.
 
 
 
== Web interface translation ==
 
 
 
See [https://projects.archlinux.org/aurweb.git/tree/doc/i18n.txt i18n.txt] in the AUR source tree for information about creating and maintaining translation of the AUR web interface.
 
  
 
== FAQ ==
 
== FAQ ==
Line 333: Line 155:
 
=== What kind of packages are permitted on the AUR? ===
 
=== What kind of packages are permitted on the AUR? ===
  
For most cases, everything is permitted, subject to the [[#Rules of submission]].
+
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 [[AUR submission guidelines#Rules of submission|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? ===
 
=== How can I vote for packages in the AUR? ===
  
See [[#Voting for packages]].
+
Sign up on the [https://aur.archlinux.org/ AUR website] to get a "Vote for this package" option while browsing packages. After signing up it is also possible to vote from the commandline with {{AUR|aurvote}}, {{AUR|aurvote-git}} or {{AUR|aur-auto-vote-git}}.
 +
 
 +
Alternatively, if you have set up [[AUR submission guidelines#Authentication|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.
 +
 
 +
$ ssh aur@aur.archlinux.org vote ''package_name''
  
=== What is a Trusted User (TU)? ===
+
=== What is a Trusted User / TU? ===
  
The [[AUR Trusted User Guidelines|Trusted Users]] are people chosen to oversee the AUR and maintain {{ic|PKGBUILD}}s in the [[community repository]].
+
A [[AUR Trusted User Guidelines|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 [[PKGBUILD]]s in ''community'', and overall keep the AUR running.
  
 
=== What is the difference between the Arch User Repository and the community repository? ===
 
=== 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.
+
The Arch User Repository is where all [[PKGBUILD]]s that users submit are stored, and must be built manually with [[makepkg]]. When {{ic|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? ===
 
=== Foo in the AUR is outdated; what should I do? ===
  
See [[#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 [[Archiving_and_compression#Archiving_only|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. This means you ask a [[Trusted User]] to disown the package base. This is to be done only if the package requires maintainer action, that he/she is not responding and you already tried to contact him/her previously.
  
 
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 {{ic|pkgver}} or {{ic|source}} array is sufficient.
 
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 {{ic|pkgver}} or {{ic|source}} array is sufficient.
 +
 +
{{Note|[[VCS package guidelines|VCS packages]] are not considered out of date when the pkgver changes, do not flag them as the maintainer will merely unflag the package and ignore you. AUR maintainers should not commit mere pkgver bumps.}}
  
 
=== Foo in the AUR does not compile when I run makepkg; what should I do? ===
 
=== Foo in the AUR does not compile when I run makepkg; what should I do? ===
  
You are probably missing something trivial; see [[#Verifying packages]].
+
You are probably missing something trivial.
 +
 
 +
# [[Pacman#Upgrading_packages|Upgrade the system]] before compiling anything with [[makepkg]] as the problem may be that your system is not up-to-date.
 +
# Ensure you have both {{Grp|base}} and {{Grp|base-devel}} groups installed.
 +
# Try using the {{ic|-s}} option with {{ic|makepkg}} to check and install all the dependencies needed before starting the build process.
 +
 
 +
Be sure to first read the [[PKGBUILD]] and the comments on the AUR page of the package in question.
 +
The reason might not be trivial after all. Custom {{ic|CFLAGS}}, {{ic|LDFLAGS}} and {{ic|MAKEFLAGS}} can cause failures. It is also possible that the {{ic|PKGBUILD}} is broken for everyone. If you cannot figure it out on your own, just report it to the maintainer e.g. by posting the errors you are getting in the comments on the AUR page.
 +
 
 +
To check if the {{ic|PKGBUILD}} is broken, or your system is misconfigured, consider building in a clean chroot. It will build your package in a clean Arch Linux environment, with only (build) dependencies installed, and without user customization. To do this [[install]] {{pkg|devtools}} and run ''extra-x86_64-build'' instead of ''makepkg''. For [[multilib]] packages, run ''multilib-build'' See [[DeveloperWiki:Building in a clean chroot]] for more information. If the build process still fails in a clean chroot, the issue is probably with the {{ic|PKGBUILD}}.
  
 
=== ERROR: One or more PGP signatures could not be verified!; what should I do? ===
 
=== ERROR: One or more PGP signatures could not be verified!; what should I do? ===
  
See [[Makepkg#ERROR: One or more PGP signatures could not be verified!]].
+
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? ===
 
=== How do I create a PKGBUILD? ===
  
Be sure to check the AUR to avoid duplicating efforts, then see [[creating packages]].
+
The best resource is the wiki page about [[creating packages]]. Remember to look in AUR before creating the [[PKGBUILD]] as to not duplicate efforts.
  
 
=== I have a PKGBUILD I would like to submit; can someone check it to see if there are any errors? ===
 
=== 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]].
+
If you would like to have your [[PKGBUILD]] reviewed, post it on the [https://mailman.archlinux.org/mailman/listinfo/aur-general aur-general mailing list] to get feedback from the TUs and fellow AUR members. You could also get help from the [[IRC channel]], #archlinux-aur on irc.freenode.net. You can also use [[namcap]] to check your {{ic|PKGBUILD}} and the resulting package for errors.
  
 
=== How to get a PKGBUILD into the community repository? ===
 
=== How to get a PKGBUILD into the community repository? ===
  
See [[#Promoting packages to the community repository]].
+
Usually, at least 10 votes are required for something to move into [[community repository|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:
 +
 
 +
* Arch Linux already has another version of a package in the repositories
 +
* Its license prohibits redistribution
 +
* It helps retrieve user-submitted [[PKGBUILD]]s. [[AUR helpers]] are [https://bbs.archlinux.org/viewtopic.php?pid=828310#p828310 unsupported] by definition.
 +
 
 +
See also [[AUR Trusted User Guidelines#Rules for Packages Entering the .5Bcommunity.5D Repo|Rules for Packages Entering the community Repo]].
  
 
=== How can I speed up repeated build processes? ===
 
=== How can I speed up repeated build processes? ===
Line 379: Line 227:
 
=== What is the difference between foo and foo-git packages? ===
 
=== 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 [[VCS package guidelines#Guidelines|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 ''makepkg'', their {{ic|pkgver}} in the AUR does not reflect upstream changes. Likewise, these packages cannot perform an authenticity checksum on any [[VCS_package_guidelines#VCS_sources|VCS source]].
+
Many AUR packages come in "stable" release and "unstable" development versions. Development packages usually have a [[VCS package guidelines#Guidelines|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 {{ic|makepkg}}, their {{ic|pkgver()}} in the AUR does not reflect upstream changes. Likewise, these packages cannot perform an authenticity checksum on any [[VCS_package_guidelines#VCS_sources|VCS source]].
  
 
See also [[System maintenance#Use proven software packages]].
 
See also [[System maintenance#Use proven software packages]].
Line 385: Line 233:
 
=== Why has foo disappeared from the AUR? ===
 
=== 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]].
+
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 [[AUR submission guidelines#Rules of submission|rules of submission]]. See the [https://lists.archlinux.org/pipermail/aur-requests/ aur-requests archives] for the reason for deletion.
  
Packages may be deleted if they did not fulfill the [[#Rules of submission]]. See the [https://lists.archlinux.org/pipermail/aur-requests/ aur-requests archives] for the reason for deletion.
+
{{Note|The git repository for a deleted package typically remain available. See [[AUR_submission_guidelines#Requests]] for details.}}
  
 
If the package used to exist in AUR3, it might not have been [https://lists.archlinux.org/pipermail/aur-general/2015-August/031322.html migrated to AUR4]. See the [[#Git repositories for AUR3 packages]] where these are preserved.
 
If the package used to exist in AUR3, it might not have been [https://lists.archlinux.org/pipermail/aur-general/2015-August/031322.html migrated to AUR4]. See the [[#Git repositories for AUR3 packages]] where these are preserved.
Line 400: Line 250:
  
 
* https://aur.archlinux.org/packages.gz
 
* https://aur.archlinux.org/packages.gz
* Use ''aurpkglist'' from {{aur|python3-aur}}
+
* Use {{ic|aurpkglist}} from {{aur|python3-aur}}
  
 
== See also ==
 
== See also ==

Latest revision as of 14:30, 16 September 2019

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).

Warning: AUR packages are user produced content. Any use of the provided files is at your own risk.

Getting started

Users can search and download PKGBUILDs from the AUR Web Interface. These PKGBUILDs can be built into installable packages using makepkg, then installed using pacman.

  • Ensure the base-devel package group is installed in full (pacman -S --needed base-devel).
  • Glance over the #FAQ for answers to the most common questions.
  • You may wish to adjust /etc/makepkg.conf to 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 aur@aur.archlinux.org help for a list of available commands.

History

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 PKGBUILDs. 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 packages

Installing packages from the AUR is a relatively simple process. Essentially:

  1. Acquire the build files, including the PKGBUILD and possibly other required files, like systemd units and patches (often not the actual code).
  2. Verify that the PKGBUILD and accompanying files are not malicious or untrustworthy.
  3. Run makepkg -si in 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.
Note: The AUR is unsupported, so any packages you install are your responsibility to update, not pacman's. If packages in the official repositories are updated, you will need to rebuild any AUR packages that depend on those libraries.

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.

Tip: Use the --needed flag when installing the base-devel group to skip packages you already have instead of reinstalling them.
Note: Packages in the AUR assume that the base-devel group is installed, i.e. they do not list the group's members as dependencies explicitly.

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:

  • 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 git pull.
  • 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
Warning: Carefully check the 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. [1]

View the contents of all provided files. For example, to use the pager less to view PKGBUILD do:

$ less PKGBUILD
Tip: If you are updating a package, you may want to look at the changes since the last commit.
  • To view changes since the last git commit you can use git show.
  • 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
  • -s/--syncdeps automatically 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.
  • -i/--install installs the package if it is built successfully. Alternatively the built package can be installed with pacman -U package_name.pkg.tar.xz.

Other useful flags are

  • -r/--rmdeps removes 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.
  • -c/--clean cleans up temporary build files after the build, as they are no longer needed. These files are usually needed only when debugging the build process.
Note: The above example is only a brief summary of the build process. It is highly recommended to read the makepkg and ABS articles for more details.

Feedback

The AUR Web Interface has a comments facility that allows users to provide suggestions and feedback on improvements to the PKGBUILD contributor. Avoid pasting patches or 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 even use a pastebin.

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!

Submitting 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. 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.

Comment syntax

The Python-Markdown syntax is supported in comments. It provides basic Markdown syntax to format comments. Note this implementation has some occasional differences with the official syntax rules. Commit hashes to the Git repository of the package and references to Flyspray tickets are converted to links automatically. Long comments are collapsed and can be expanded on demand.

FAQ

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?

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?

Sign up on the AUR website to get a "Vote for this package" option while browsing packages. After signing up it is also possible to vote from the commandline with aurvoteAUR, aurvote-gitAUR or aur-auto-vote-gitAUR.

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.

$ ssh aur@aur.archlinux.org vote package_name

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 PKGBUILDs 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?

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. This means you ask a Trusted User to disown the package base. This is to be done only if the package requires maintainer action, that he/she is not responding and you already tried to contact him/her previously.

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.

Note: VCS packages are not considered out of date when the pkgver changes, do not flag them as the maintainer will merely unflag the package and ignore you. AUR maintainers should not commit mere pkgver bumps.

Foo in the AUR does not compile when I run makepkg; what should I do?

You are probably missing something trivial.

  1. Upgrade the system before compiling anything with makepkg as the problem may be that your system is not up-to-date.
  2. Ensure you have both base and base-devel groups installed.
  3. Try using the -s option with makepkg to check and install all the dependencies needed before starting the build process.

Be sure to first read the PKGBUILD and the comments on the AUR page of the package in question. The reason might not be trivial after all. Custom CFLAGS, LDFLAGS and MAKEFLAGS can cause failures. It is also possible that the PKGBUILD is broken for everyone. If you cannot figure it out on your own, just report it to the maintainer e.g. by posting the errors you are getting in the comments on the AUR page.

To check if the PKGBUILD is broken, or your system is misconfigured, consider building in a clean chroot. It will build your package in a clean Arch Linux environment, with only (build) dependencies installed, and without user customization. To do this install devtools and run extra-x86_64-build instead of makepkg. For multilib packages, run multilib-build See DeveloperWiki:Building in a clean chroot for more information. If the build process still fails in a clean chroot, the issue is probably with the PKGBUILD.

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?

The best resource is the wiki page about creating packages. Remember to look in AUR before creating the PKGBUILD as to not duplicate efforts.

I have a PKGBUILD I would like to submit; can someone check it to see if there are any errors?

If you would like to have your PKGBUILD reviewed, post it on the aur-general mailing list to get feedback from the TUs and fellow AUR members. You could also get help from the IRC channel, #archlinux-aur on irc.freenode.net. You can also use namcap to check your PKGBUILD and the resulting package for errors.

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:

  • Arch Linux already has another version of a package in the repositories
  • Its license prohibits redistribution
  • It helps retrieve user-submitted PKGBUILDs. AUR helpers are unsupported by definition.

See also Rules for Packages Entering the community Repo.

How can I speed up repeated build processes?

See Makepkg#Improving compile times.

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 makepkg, their pkgver() in the AUR does not reflect upstream changes. Likewise, these packages cannot perform an authenticity checksum on any VCS source.

See also System maintenance#Use proven software 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.

Note: The git repository for a deleted package typically remain available. See AUR_submission_guidelines#Requests for details.

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:

$ 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?

See also