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|delta> [<package|delta> ...]
10 repo-remove [options] <path-to-db> <packagename|delta>
12 [<packagename|delta> ...]
13
15 repo-add and repo-remove are two scripts to help build a package
16 database for packages built with makepkg(8) and installed with
17 pacman(8). They also handle package deltas produced by pkgdelta(8).
18 repo-add will update a package database by reading a built package or
20 package delta file. Multiple packages and/or deltas to add can be
21 specified on the command line.
22 If a matching “.sig” file is found alongside a package file, the
24 signature will automatically be embedded into the database.
25 repo-remove will update a package database by removing the package name
27 or delta specified on the command line. Multiple packages and/or delta
28 to remove can be specified on the command line.
29 A package database is a tar file, optionally compressed. Valid
31 extensions are “.db” followed by an archive extension of “.tar”,
32 “.tar.gz”, “.tar.bz2”, “.tar.xz”, or “.tar.Z”. The file does not need
33 to exist, but all parent directories must exist.
34
36 -q, --quiet
37 Force this program to keep quiet and run silently except for
38 warning and error messages.
39 -s, --sign
41 Generate a PGP signature file using GnuPG. This will execute gpg
42 --detach-sign --use-agent on the generated database to generate a
43 detached signature file, using the GPG agent if it is available.
44 The signature file will be the entire filename of the database with
45 a “.sig” extension.
46 -k, --key <key>
48 Specify a key to use when signing packages. Can also be specified
49 using the GPGKEY environmental variable. If not specified in either
50 location, the default key from the keyring will be used.
51 -v, --verify
53 Verify the PGP signature of the database before updating the
54 database. If the signature is invalid, an error is produced and the
55 update does not proceed.
56 --nocolor
58 Remove color from repo-add and repo-remove output.
59
61 -d, --delta
62 Automatically generate and add a delta file between the old entry
63 and the new one, if the old package file is found next to the new
64 one.
65 -n, --new
67 Only add packages that are not already in the database. Warnings
68 will be printed upon detection of existing packages, but they will
69 not be re-added.
70 -R, --remove
72 Remove old package files from the disk when updating their entry in
73 the database.
74
76 repo-add foo.db.tar.xz <pkg1> [<pkg2> ...]
77 This creates two separate databases; a smaller database “foo.db.tar.xz”
79 used by pacman and a large database containing package file lists
80 “foo.files.tar.xz” for use by other utilities. While pacman can use the
81 large database (if renamed with a db.tar* extension), there is
82 currently no additional benefit for the larger download.
83
85 makepkg(8), pacman(8), pkgdelta(8)
86 See the pacman website at https://www.archlinux.org/pacman/ for current
88 information on pacman and its related tools.
89
91 Bugs? You must be kidding; there are no bugs in this software. But if
92 we happen to be wrong, send us an email with as much detail as possible
93 to pacman-dev@archlinux.org.
94
96 Current maintainers:
97 · Allan McRae <allan@archlinux.org>
99 · Andrew Gregory <andrew.gregory.8@gmail.com>
101 · Dan McGee <dan@archlinux.org>
103 · Dave Reisner <dreisner@archlinux.org>
105 Past major contributors:
107 · Judd Vinet <jvinet@zeroflux.org>
109 · Aurelien Foret <aurelien@archlinux.org>
111 · Aaron Griffin <aaron@archlinux.org>
113 · Xavier Chantry <shiningxc@gmail.com>
115 · Nagy Gabor <ngaba@bibl.u-szeged.hu>
117 For additional contributors, use git shortlog -s on the pacman.git
119 repository.
120Pacman 5.0.2 2019-02-02 REPO-ADD(8)