Arch linux aur repository

Arch Linux User Repository

Welcome to the AUR! Please read the AUR User Guidelines for more information and the AUR Submission Guidelines if you want to contribute a PKGBUILD. Contributed PKGBUILDs must conform to the Arch Packaging Standards otherwise they will be deleted! Remember to vote for your favourite packages! Some packages may be provided as binaries in [community].

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

Support

Package Requests

There are three types of requests that can be filed in the Package Actions box on the package details page:

• Orphan Request: Request a package to be disowned, e.g. when the maintainer is inactive and the package has been flagged out-of-date for a long time.
• Deletion Request: Request a package to be removed from the Arch User Repository. Please do not use this if a package is broken and can be fixed easily. Instead, contact the package maintainer and file orphan request if necessary.
• Merge Request: Request a package to be merged into another one. Can be used when a package needs to be renamed or replaced by a split package.

If you want to discuss a request, you can use the aur-requests mailing list. However, please do not use that list to file requests.

Submitting Packages

Git over SSH is now used to submit packages to the AUR. See the Submitting packages section of the Arch User Repository ArchWiki page for more details.

The following SSH fingerprints are used for the AUR:

• Ed25519 : SHA256:RFzBCUItH9LZS0cKB5UE6ceAYhBD5C8GeOBip8Z11+4
• ECDSA : SHA256:uTa/0PndEgPZTf76e1DFqXKJEXKsn7m9ivhLQtzGOCI
• RSA : SHA256:5s5cIyReIfNNVGRFdDbe3hdYiI5OelHGpw2rOUud3Q8

Discussion

General discussion regarding the Arch User Repository (AUR) and Trusted User structure takes place on aur-general. For discussion relating to the development of the AUR web interface, use the aur-dev mailing list.

Bug Reporting

If you find a bug in the AUR web interface, please fill out a bug report on our bug tracker. Use the tracker to report bugs in the AUR web interface only. To report packaging bugs contact the package maintainer or leave a comment on the appropriate package page.

Recent Updates (more)

timg 1.5.1-1	2023-07-17 06:55 (UTC)
candy 1.16-1	2023-07-17 06:54 (UTC)
quarto-cli-pre-release 1.4.230-1	2023-07-17 06:51 (UTC)
jackett-bin 0.21.484-1	2023-07-17 06:40 (UTC)
jackett 0.21.484-1	2023-07-17 06:40 (UTC)
sing-box-beta 1.3.1.beta.3-1	2023-07-17 06:39 (UTC)
jackett-mono 0.21.484-1	2023-07-17 06:39 (UTC)
trojita 0.7-10	2023-07-17 06:38 (UTC)
qovery-cli 0.60.0-1	2023-07-17 06:37 (UTC)
python-dbx 0.8.18-1	2023-07-17 06:28 (UTC)
python-h5pyd 0.15.1-1	2023-07-17 06:23 (UTC)
python-h5pyd-doc 0.15.1-1	2023-07-17 06:23 (UTC)
opentodolist 3.45.0-1	2023-07-17 06:20 (UTC)
overgrowth-game-git 20230517.594a2a4-1	2023-07-17 06:12 (UTC)
greptimedb-bin 0.4.0.20230717-1	2023-07-17 06:10 (UTC)

Statistics

Packages	85745
Orphan Packages	11013
Packages added in the past 7 days	279
Packages updated in the past 7 days	1732
Packages updated in the past year	27933
Packages never updated	20331
Registered Users	106713
Trusted Users	63

Copyright © 2004-2023 aurweb Development Team.

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

Источник

What is Arch User Repository (AUR)? How to Use AUR on Arch and Manjaro Linux?

If you have been using Arch Linux or other distributions based on Arch such as Manjaro, you might have come across the term AUR. You try to install new software and someone suggests installing it from AUR. This leaves you confused. What is this AUR? Why is it used? How to use AUR? I’ll answer these questions in this article.

What is AUR?

AUR stands for Arch User Repository. It is a community-driven repository for Arch-based Linux distribution users. It contains package descriptions named PKGBUILDs that allow you to compile a package from source with makepkg and install it via pacman, the package manager in Arch Linux. The AUR was created to organize and share new packages from the community and to help accelerate popular packages’ inclusion into the community repository. Many 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 can 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.

In short, AUR is the way for developers to make new software available to Arch Linux users before the software is officially included in Arch repositories.

Should you use AUR? What’s the risk involved?

Using the AUR is like crossing the street. If you proceed with caution you should be fine. If you are new to Linux it is advised not to use the AUR until you build a foundation knowledge about Arch/Manjaro and Linux in general. It is true that anyone can upload packages to the AUR but the Trusted Users (TUs) are charged with keeping an eye on what gets uploaded. Although TUs perform quality control on the uploaded packages, there is no guarantee that packages in the AUR are well-formed or not malicious. In practice, the AUR seems to be quite safe but in theory, it can do some damage, but only if you are not careful. A smart Arch user always inspects PKGBUILDs and *.install files when building packages from the AUR. Additionally, TUs (Trusted Users) also remove packages in the AUR that are included in core/extra/community so there should be no naming conflicts between them. The AUR will often contain developmental versions of packages (cvs/svn/git/etc) but they will have modified names such as foo-git. As for the AUR packages, pacman handles dependency resolution and detects file conflicts. You never have to worry about overwriting files in one package with files from another unless you use the —force option by default. If you do that, you probably have more serious problems than file conflicts.

How to use AUR?

The simplest way to use AUR is through an AUR helper. An AUR helper is a command line tool (some have GUI as well) that lets you search for packages published on the AUR and install them.

Installing an AUR helper on Arch Linux

Let’s say you want to use Yay AUR helper. Make sure that you have git installed on Linux. And then clone the repository, go to the directory and build the package. Use these commands one by one for that:

sudo pacman -S --needed git base-devel git clone https://aur.archlinux.org/yay.git cd yay makepkg -si

It’s not that you must use AUR helper for installing packages from AUR. The next section shows how to use AUR without an AUR helper.

Installing AUR packages without AUR helpers

If you don’t want to use AUR helper, you can still install packages from AUR. You have to build them with a few commands. As soon as you find the package you want to install on AUR page it is advised to confirm “Licence”, “Popularity”, “Last Updated”, “Dependencies” and so on as an extra quality control step.

git clone [package URL] cd [package name] makepkg -si

git clone https://aur.archlinux.org/telegram-desktop-git.git cd telegram-desktop-git makepkg -si

Enabling AUR support in Manjaro Linux

AUR isn’t enabled by default and you have to enable it through pamac. My laptop runs Manjaro Cinnamon but the steps are the same for all Manjaro flavors. Open Pamac (listed as Add/Remove Software): Once you are in pamac go to preferences like shown below. In the preferences dialog box go to the AUR tab, enable the AUR support, enable check for updates and close the dialog box. You can now search for packages and those which belong to AUR can be identified by the tag under the package descriptions. AUR is one of the many reasons why people love Arch Linux and you can see why it is so popular. I hope you find this article useful and keep an eye on social media for upcoming Arch-related topics.

Источник