How to Update Outdated Packages in the Arch User Repository (AUR)

If you’ve ever encountered an outdated package in the Arch User Repository (AUR) and wondered how to contribute to its maintenance, this guide outlines the straightforward steps involved in updating an AUR package, using Pyspread as an illustrative example. This process is invaluable for any aspiring AUR package maintainer.

1. Clone the Package Repository

The initial step involves obtaining the package’s repository. Use the git clone command with the appropriate SSH address for the AUR package, then navigate into the newly created directory. For instance, to update Pyspread, you’d execute:

git clone ssh://[email protected]/pyspread.git
cd pyspread

2. Update the PKGBUILD File

Next, you need to modify the PKGBUILD file, which contains instructions for building the package. This involves several critical changes:

• Adjust the pkgver variable: Update it to reflect the new software version (e.g., pkgver=2.4).
• Update the source tarball: Modify the source array to point to the latest source archive, typically found on PyPI or the project’s official release page.
• Replace sha256sums: Generate new checksums for the updated source files to ensure integrity and replace the old ones in the PKGBUILD.

3. Regenerate .SRCINFO

After modifying the PKGBUILD, it’s essential to regenerate the .SRCINFO file. This file contains metadata about the package in a format that the AUR uses to display information. Execute the following command:

makepkg --printsrcinfo > .SRCINFO

4. Test Build Locally

Before pushing your changes, always perform a local test build to confirm everything works as expected and the package installs correctly. The makepkg -si command will build the package and install it, allowing you to verify its functionality:

makepkg -si

5. Commit and Push Changes

Once you’ve verified the package builds successfully and functions as intended, commit your changes and push them back to the AUR. Stage both the PKGBUILD and .SRCINFO files, commit with a clear and descriptive message, and then push:

git add PKGBUILD .SRCINFO
git commit -m "Update to version 2.4"
git push

With these steps completed, your updated package will be live on the AUR, accessible to all users. This process highlights the collaborative spirit of the Arch Linux community; even seemingly minor contributions like a package version bump play a crucial role in keeping the software ecosystem current and reliable for everyone.