1REPO-ADD(8) Pacman Manual REPO-ADD(8)
2
6 repo-add - package database maintenance utility
7
9 repo-add [options] <path-to-db> <package> [<package> ...]
10 repo-remove [options] <path-to-db> <packagename> [<packagename> ...]
12
14 repo-add and repo-remove are two scripts to help build a package
15 database for packages built with makepkg(8) and installed with
16 pacman(8).
17 repo-add will update a package database by reading a built package
19 file. Multiple packages to add can be specified on the command line.
20 If a matching “.sig” file is found alongside a package file, the
22 signature will automatically be embedded into the database.
23 repo-remove will update a package database by removing the package name
25 specified on the command line. Multiple packages to remove can be
26 specified on the command line.
27 A package database is a tar file, optionally compressed. Valid
29 extensions are “.db” followed by an archive extension of “.tar”,
30 “.tar.gz”, “.tar.bz2”, “.tar.xz”, or “.tar.Z”. The file does not need
31 to exist, but all parent directories must exist.
32
34 -q, --quiet
35 Force this program to keep quiet and run silently except for
36 warning and error messages.
37 -s, --sign
39 Generate a PGP signature file using GnuPG. This will execute gpg
40 --detach-sign --use-agent on the generated database to generate a
41 detached signature file, using the GPG agent if it is available.
42 The signature file will be the entire filename of the database with
43 a “.sig” extension.
44 -k, --key <key>
46 Specify a key to use when signing packages. Can also be specified
47 using the GPGKEY environmental variable. If not specified in either
48 location, the default key from the keyring will be used.
49 -v, --verify
51 Verify the PGP signature of the database before updating the
52 database. If the signature is invalid, an error is produced and the
53 update does not proceed.
54 --nocolor
56 Remove color from repo-add and repo-remove output.
57
59 -n, --new
60 Only add packages that are not already in the database. Warnings
61 will be printed upon detection of existing packages, but they will
62 not be re-added.
63 -R, --remove
65 Remove old package files from the disk when updating their entry in
66 the database.
67
69 repo-add foo.db.tar.xz <pkg1> [<pkg2> ...]
70 This creates two separate databases; a smaller database “foo.db.tar.xz”
72 used by pacman and a large database containing package file lists
73 “foo.files.tar.xz” for use by other utilities. While pacman can use the
74 large database (if renamed with a db.tar* extension), there is
75 currently no additional benefit for the larger download.
76
78 makepkg(8), pacman(8)
79 See the pacman website at https://www.archlinux.org/pacman/ for current
81 information on pacman and its related tools.
82
84 Bugs? You must be kidding; there are no bugs in this software. But if
85 we happen to be wrong, submit a bug report with as much detail as
86 possible at the Arch Linux Bug Tracker in the Pacman section.
87
89 Current maintainers:
90 · Allan McRae <allan@archlinux.org>
92 · Andrew Gregory <andrew.gregory.8@gmail.com>
94 · Dan McGee <dan@archlinux.org>
96 · Dave Reisner <dreisner@archlinux.org>
98 Past major contributors:
100 · Judd Vinet <jvinet@zeroflux.org>
102 · Aurelien Foret <aurelien@archlinux.org>
104 · Aaron Griffin <aaron@archlinux.org>
106 · Xavier Chantry <shiningxc@gmail.com>
108 · Nagy Gabor <ngaba@bibl.u-szeged.hu>
110 For additional contributors, use git shortlog -s on the pacman.git
112 repository.
113Pacman 5.2.1 2020-04-01 REPO-ADD(8)