table of contents
- bullseye-backports 6.0.2-3~bpo11+1
- testing 6.0.2-3
- unstable 6.0.2-3
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 pacman(8).
repo-add will update a package database by reading a built package file. Multiple packages to add can be specified on the command line.
If a matching “.sig” file is found alongside a package file, the signature will automatically be embedded into the database.
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.
-k, --key <key>
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 download.
See the pacman website at https://archlinux.org/pacman/ for current information on pacman and its related tools.
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.
Past major contributors:
For additional contributors, use git shortlog -s on the pacman.git repository.