1yumdb(8)                                                              yumdb(8)
2
3
4

NAME

6       yumdb command
7

SYNOPSIS

9       yumdb [command] [packages ...]
10

DESCRIPTION

12       This  command  is  used to query and alter the yum database, which is a
13       simple key value store used in conjunction with the rpm  database.  Any
14       installed  package can have arbitrary data in the yum database, however
15       the main use case is to store extra data about  packages  as  they  are
16       installed.
17
18       yumdb commands are:
19
20       yumdb get <key> [pkg-wildcard]...
21
22       This  command  will  get  the  value for the given key, limiting to any
23       specified packages.
24
25       yumdb set <key> <value> [pkg-wildcard]...
26
27       This command will set the value for the given key, to the given  value,
28       limiting to any specified packages.
29
30       yumdb del <key> [pkg-wildcard]...
31
32       This command will delete the given key, limiting to any specified pack‐
33       ages.
34
35       yumdb rename <old-key> <new-key> [pkg-wildcard]...
36
37       This command will rename the given old-key, to the given new-key,  lim‐
38       iting to any specified packages. If the old-key does not exist, nothing
39       happens.
40
41       yumdb rename-force <old-key> <new-key> [pkg-wildcard]...
42
43       This command will rename the given old-key, to the given new-key,  lim‐
44       iting to any specified packages. If the old-key does not exist, new-key
45       is deleted.
46
47       yumdb copy <old-key> <new-key> [pkg-wildcard]...
48
49       This command will copy the given old-key, to the given new-key,  limit‐
50       ing  to  any specified packages. If the old-key does not exist, nothing
51       happens.
52
53       yumdb copy-force <old-key> <new-key> [pkg-wildcard]...
54
55       This command will copy the given old-key, to the given new-key,  limit‐
56       ing  to  any specified packages. If the old-key does not exist, new-key
57       is deleted.
58
59       yumdb search <key> <wildcard>...
60
61       This command will search all packages for the given key, against any of
62       the given wildcard values.
63
64       yumdb exist <key> [pkg-wildcard]...
65
66       This command will print any packages which have the given key, limiting
67       to any specified packages.
68
69       yumdb unset <key> [pkg-wildcard]...
70
71       This command will print any packages which do not have the  given  key,
72       limiting to any specified packages.
73
74       yumdb info [pkg-wildcard]...
75
76       This command will display all the data stored in the yumdb, limiting to
77       any specified packages.
78
79       yumdb sync [pkg-wildcard]...
80
81       This command will add any missing data to the yumdb from the  reposito‐
82       ries,  limiting to any specified packages. This is useful to run if you
83       have had any aborted transactions (and thus. missing yumdb data).  Note
84       that  "yumdb sync" cannot know all the information that would have been
85       put into the yumdb at the time.
86
87       yumdb sync-force [pkg-wildcard]...
88
89       This command will replace any data in the yumdb from the  repositories,
90       limiting to any specified packages.
91
92

EXAMPLES

94       List all the packages which don't have a from_repo key/value:
95
96              yumdb unset from_repo
97
98       List all the packages which were installed as dependencies:
99
100              yumdb search reason dep
101
102

WELL KNOWN KEYS

104       Note  that  there is no limit to the number of keys that can be created
105       or what they may contain (for installed packages only). However this is
106       a list of well known keys, and what they store.
107
108       checksum_data
109
110       checksum_type
111
112       These keys store the createrepo checksum, and it's type, of the available
113       package yum installed. Note that these are used by "yum version" to calculate
114       the rpmdb version.
115
116       command_line
117
118       This key stores the entire command line, of the yum command (if it was called).
119
120       from_repo
121
122       from_repo_revision
123
124       from_repo_timestamp
125
126       These keys take values from the available package yum installed, and store the
127       repo id, it's revision and timestamp.
128
129       reason
130
131       This key stores either "user" or "dep", currently. To mark if the user requested
132       the package to be installed, or if it was brought in automatically as a
133       dependency. Note that this is kept over updates.
134
135       releasever
136
137       This key stores the value of releasever, when the package was installed.
138
139       installonly
140
141       If this attribute has the value "keep" then this package will not be
142       removed automatically by the installonly process (and does not count towards
143       the installonly_limit).
144
145

SEE ALSO

147       yum (8)
148       rpm (8)
149
150

AUTHORS

152       James Antill <james.antill@redhat.com>.
153
154
155
156
157James Antill                     8 April 2010                         yumdb(8)