AUR Trusted User Guidelines

From ArchWiki
Revision as of 19:03, 23 July 2009 by Pressh (talk | contribs) (Changed protection level for "AUR Trusted User Guidelines" ([edit=sysop] (indefinite) [move=sysop] (indefinite)))
Jump to navigation Jump to search

Template:Article summary start Template:Article summary text Template:Article summary heading Template:I18n entry Template:I18n entry Template:I18n entry Template:Article summary heading Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary end

The Trusted User (TU)

The Trusted User (TU) is a member of the community charged with keeping the AUR in working order. He/she maintains popular packages, and votes in administrative matters. A TU is elected from active community members by current TUs in a democratic process. TUs are the only members who have a final say in the direction of the AUR.

The TUs are governed using the TU bylaws

TU Duties

TODO list for new Trusted Users

  • Install the devtools package.
  • Send your ssh public key to Loui Chang. If you don't have one, use ssh-keygen to generate. You can check the [Using SSH Keys]] wiki page for more information about creating ssh keys and setting up an ssh-agent to use them.
  • Make the directory staging/community within your home directory on This step is important as the devtools scripts use this directory to process incoming packages.
  • Remind Allan to change your account on forums
  • Make sure your sponsor has given you TU status on the AUR
  • Ask some TU for the #archlinux-tu@freenode key
  • Add yourself to the Trusted Users page
  • Read the Trusted User Guidelines.
  • If you are not upgraded to a Trusted User group on bugtracker in two days, report this as a bug to Roman
  • Ask Aaron for access to the x86_64 build machine if you need it (when it comes back online)
  • Start contributing!


The TUs should also make an effort to check package submissions in UNSUPPORTED for malicious code and good PKGBUILDing standards. In around 80% of cases the PKGBUILDs in the UNSUPPORTED are very simple and can be quickly checked for sanity and malicious code by the TU team.

TUs should also check PKGBUILDs for minor mistakes, suggest corrections and improvements. The TU should endeavor to confirm that all pkgs follow the Arch Packaging Guidelines/Standards and in doing so share their skills with other package builders in an effort to raise the standard of package building across the distro.

TUs are also in an excellent position to document recommended practices.

The TU and [community], Guidelines for Package Maintenance

Rules for Packages Entering the [community] Repo

Any packages to be added to the [community] repo must meet the guidelines listed on this page.

Accessing and Updating the Repository

The [community] repository now uses devtools which is the same system used for uploading packages to [core] and [extra], except that it uses another server instead of Thus most of the instructions in Packager Guide work without any change. Information which is specific for the [community] repository (like changed URLs) have been put here.

Initially you should do a non-recursive checkout of the [community] repository:
svn checkout -N svn+ssh://

This creates a directory named "svn-packages" which contains nothing. It does, however, know that it is an svn checkout.

For checking out, updating all packages or adding a package see the Packager Guide.

To remove a package
ssh /arch/db-remove community pkgname arch

Here and in the following text, arch can be one of i686 or x86_64 which are the two architectures supported by Arch Linux.

When you're done with editing the PKGBUILD, etc, you should commit the changes (svn commit).
When you want to release a package, first copy the package to the staging/community directory on using scp and then tag the package by going to the pkgname/trunk directory and issuing archrelease community-arch.

This makes an svn copy of the trunk entries in a directory named community-i686 or community-x86_64 indicating that this package is in the community repository for that architecture.

Note: In some cases, especially for community packages, an x86_64 TU might bump the pkgrel by .1 (and not +1). This indicates that the change to the PKGBUILD is x86_64 specific and i686 maintainers should not rebuild the package for i686. When the TU decides to bump the pkgrel , it should be done with the usual increment of +1. However, a previous pkgrel=2.1 must not become pkgrel=3.1 when bumped by the TU and must instead be pkgrel=3. In a nutshell, leave dot (.) releases exclusive to the x86_64 TU's to avoid confusion.

Thus the process of updating a package can be summarised as

  • Update the package directory (svn update some-package)
  • Change to the package trunk directory (cd some-package/trunk)
  • Edit the PKGBUILD, make necessary changes and makepkg. It is recommended to build in a clean chroot.
  • Namcap the PKGBUILD and the binary pkg.tar.gz.
  • Commit the changes to trunk (svn commit)
  • Copy the package to (scp pkgname-ver-rel-arch.pkg.tar.gz
  • Tag the package (archrelease community-{i686,x86_64})
  • Update the repository (ssh /arch/db-community{,64})

Also see the Miscellaneous section in the Packager Guide. For the section Avoid having to enter your password all the time use instead of and

Disowning packages

If a TU can't or doesn't want to maintain a package any longer, a notice should be posted to the AUR Mailing List, so another TU can maintain it. A package can still be disowned even if no other TU wants to maintain it, but the TUs should try not to drop many packages (they shouldn't take on more than they have time for). If a package has become obsolete or isn't used any longer, it can be removed completely as well.

If a package has been removed completely, it can be uploaded once again (fresh) to UNSUPPORTED, where a regular user can maintain the package instead of the TU.

Deleting packages from unsupported

There's no point in removing dummy packages, because they will be re-created in an attempt to track dependencies. If someone uploads a real package then all dependents will point to the correct place.

For an example of a dummy package see:

Moving packages from [community] to unsupported

Remove the package using the instructions above and upload your source tarball to the AUR.