repo-add - package database maintenance utility
repo-add [options] <path-to-db> <package> [<package>
repo-remove [options] <path-to-db>
<packagename> [<packagename> ...]
repo-add and repo-remove are two scripts to help build a package
database for packages built with makepkg(8) and installed with
repo-add will update a package database by reading a built
package file. Multiple packages to add can be specified on the command
If a matching “.sig” file is found alongside a
package file, the signature will automatically be embedded into the
repo-remove will update a package database by removing the
package name specified on the command line. Multiple packages to remove can
be specified on the command line.
A package database is a tar file, optionally compressed. Valid
extensions are “.db” followed by an archive extension of
“.tar”, “.tar.gz”, “.tar.bz2”,
“.tar.xz”, or “.tar.Z”. The file does not need
to exist, but all parent directories must exist.
Force this program to keep quiet and run silently except
for warning and error messages.
Generate a PGP signature file using GnuPG. This will
execute gpg --detach-sign --use-agent on the generated database to generate a
detached signature file, using the GPG agent if it is available. The signature
file will be the entire filename of the database with a “.sig”
-k, --key <key>
Specify a key to use when signing packages. Can also be
specified using the GPGKEY environmental variable. If not specified in either
location, the default key from the keyring will be used.
Verify the PGP signature of the database before updating
the database. If the signature is invalid, an error is produced and the update
does not proceed.
Remove color from repo-add and repo-remove
Only add packages that are not already in the database.
Warnings will be printed upon detection of existing packages, but they will
not be re-added.
Remove old package files from the disk when updating
their entry in the database.
repo-add foo.db.tar.xz <pkg1> [<pkg2> ...]
This creates two separate databases; a smaller database
“foo.db.tar.xz” used by pacman and a large database containing
package file lists “foo.files.tar.xz” for use by other
utilities. While pacman can use the large database (if renamed with a
db.tar* extension), there is currently no additional benefit for the larger
Bugs? You must be kidding; there are no bugs in this software. But if we happen
to be wrong, submit a bug report with as much detail as possible at the Arch
Linux Bug Tracker in the Pacman section.
•Allan McRae <email@example.com>
Past major contributors:
•Judd Vinet <firstname.lastname@example.org>
•Aaron Griffin <email@example.com>
•Dan McGee <firstname.lastname@example.org>
•Xavier Chantry <email@example.com>
•Nagy Gabor <firstname.lastname@example.org>
•Dave Reisner <email@example.com>
For additional contributors, use git shortlog -s on the pacman.git