1yumdb(8) yumdb(8)
2
3
4
6 yumdb command
7
9 yumdb [command] [packages ...]
10
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 search <key> <wildcard>...
54
55 This command will search all packages for the given key, against any of
56 the given wildcard values.
57
58 yumdb exist <key> [pkg-wildcard]...
59
60 This command will print any packages which have the given key, limiting
61 to any specified packages.
62
63 yumdb unset <key> [pkg-wildcard]...
64
65 This command will print any packages which do not have the given key,
66 limiting to any specified packages.
67
68 yumdb info [pkg-wildcard]...
69
70 This command will all the data stored in the yumdb, limiting to any
71 specified packages.
72
73
75 List all the packages which don't have a from_repo key/value:
76
77 yumdb unset from_repo
78
79 List all the packages which were installed as dependencies:
80
81 yumdb search reason dep
82
83
85 Note that there is no limit to the number of keys that can be created
86 or what they may contain (for installed packages only). However this is
87 a list of well known keys, and what they store.
88
89 checksum_data
90
91 checksum_type
92
93 These keys store the createrepo checksum, and it's type, of the available
94 package yum installed. Note that these are used by "yum version" to calculate
95 the rpmdb version.
96
97 command_line
98
99 This key stores the entire command line, of the yum command (if it was called).
100
101 from_repo
102
103 from_repo_revision
104
105 from_repo_timestamp
106
107 These keys take values from the available package yum installed, and store the
108 repo id, it's revision and timestamp.
109
110 reason
111
112 This key stores either "user" or "dep", currently. To mark if the user requested
113 the package to be installed, or if it was brought in automatically as a
114 dependency. Note that this is kept over updates.
115
116 releasever
117
118 This key stores the value of releasever, when the package was installed.
119
120 installonly
121
122 If this attribute has the value "keep" then this package will not be
123 removed automatically by the installonly process (and does not count towards
124 the installonly_limit).
125
126
128 yum [4m(8)
129 rpm [4m(8)
130
131
133 James Antill <james.antill@redhat.com>.
134
135
136
137
138James Antill 8 April 2010 yumdb(8)