1BODHI(1) bodhi BODHI(1)
2
6 bodhi - manage Fedora updates
7
9 bodhi COMMAND SUBCOMMAND [OPTIONS] [ARGS]…
10
12 bodhi is the command line interface to bodhi, Fedora’s update release
13 management system. It can be used to create or modify updates and over‐
14 rides.
15
17 Most of the commands will accept these options:
18 --debug
20 Some commands accept this flag to show extra debug information.
21 --help
23 Show help text and exit.
24 --password <text>
26 A password to authenticate as the user given by --user.
27 --staging
29 Use the staging bodhi instance instead of the production instance.
30 --url <url>
32 Use the Bodhi server at the given URL instead of the default server.
33 This can also be set with the BODHI_URL environment variable. This
34 is ignored if the --staging flag is set.
35 --user <username>
37 Many commands accept this flag to specify a Fedora username to
38 authenticate with. Note that some read operations such as querying
39 updates and overrides use this same flag, but as a search parameter
40 instead of authentication (as authentication is not required for
41 these operations).
42 --version
44 Show version and exit. Not accepted by subcommands.
45
47 There are four commands, composes, overrides, updates and releases.
48 They are described in more detail in their own sections below.
49 bodhi composes <subcommand> [options] [args]
51 Provides an interface to view composes. Supports subcommands list
52 and info, described below.
53 bodhi overrides <subcommand> [options] [args]
55 Provides commands to aid in management of build overrides. Supports
56 subcommands query and save, described below.
57 bodhi updates <subcommand> [options] [args]
59 Provides an interface to manage updates. Supports subcommands com‐
60 ment, download, new, query, and request, described below.
61 bodhi releases <subcommand> [options] [args]
63 Provides an interface to manage releases. Supports subcommands cre‐
64 ate, edit, info and list, described below.
65
67 The composes command allows users to view composes.
68 bodhi composes list [options]
70 The list subcommand allows you to see the current composes on the
71 Bodhi server. It supports the following options:
72 -v, --verbose
74 Print more detail about the composes.
75 bodhi composes info [options] RELEASE REQUEST
77 The info subcommand allows you to see the compose for release with
78 the given request.
79
81 The overrides command allows users to manage build overrides.
82 bodhi overrides query [options]
84 The query subcommand provides an interface for users to query the
85 bodhi server for existing overrides. The query subcommand supports
86 the following options:
87 --mine
89 Show only your overrides.
90 --active
92 Filter for only active overrides
93 --expired
95 Filter for only expired overrides
96 --packages <packagename>
98 Query for overrides related to the given packages, given as a
99 comma-separated list.
100 --releases <releases>
102 Query for overrides related to a list of releases, given as a
103 comma-separated list. <releases> is the release shortname, for
104 example: F26 or F26,F25
105 --builds <builds>
107 Query for overrides for a list of builds, given as a comma-sepa‐
108 rated list. <builds> is the build NVR, for example: core‐
109 bird-1.3-0.fc24
110 --user <username>
112 Filter for overrides by a list of usernames, given as a
113 comma-separated list.
114 --rows <integer>
116 Limits number of results shown per page.
117 --page <integer>
119 Go to page number.
120 bodhi overrides save [options] <nvr>
122 Save the build root given by <nvr> as a buildroot override. The save
123 subcommand supports the following options:
124 --duration <days>
126 The number of days the override should exist, given as an inte‐
127 ger.
128 --notes <text>
130 Notes on why this override is in place.
131 bodhi overrides edit [options] <nvr>
133 Edit the build root given by <nvr> as a buildroot override. The edit
134 subcommand supports the same options than the save command and also
135 the following option:
136 --expire
138 Force an override to the expired state.
139
141 The updates command allows users to interact with bodhi updates.
142 bodhi updates comment [options] <update> <text>
144 Leave the given text as a comment on a bodhi update. The comment
145 subcommand supports the following options:
146 --karma [+1 | 0 | -1]
148 The karma value you wish to contribute to the update.
149 bodhi updates download [options]
151 Download update(s) given by ID(s) or NVR(s). One of --updateid or
152 builds is required. The download subcommand supports the following
153 options:
154 --debuginfo
156 Include debuginfo packages when downloading.
157 --updateid <ids>
159 A comma-separated list of update IDs you would like to download.
160 --builds <nvrs>
162 A comma-separated list of NVRs that identify updates you would
163 like to download.
164 --arch <arch>
166 You can specify an architecture of packages to download. “all”
167 will download packages for all architectures. Omitting this
168 option will download packages for the architecture you are cur‐
169 rently running.
170 bodhi updates new [options] <builds>
172 Create a new bodhi update containing the builds, given as a comma
173 separated list of NVRs. The new subcommand supports the following
174 options:
175 --type [security | bugfix | enhancement | newpackage]
177 The type of the new update.
178 --notes <text>
180 The description of the update.
181 --notes-file <path>
183 A path to a file containing a description of the update.
184 --bugs <bugs>
186 A comma separated list of bugs to associate with this update.
187 --close-bugs
189 If given, this flag will cause bodhi to close the referenced
190 bugs automatically when the update reaches stable.
191 --request [testing | stable | upush]
193 The repository requested for this update.
194 --autokarma
196 Enable autokarma for this update.
197 --stable-karma <integer>
199 Configure the stable karma threshold for the given value.
200 --unstable-karma <integer>
202 Configure the unstable karma threshold for the given value.
203 --suggest [logout | reboot]
205 Suggest that the user logout or reboot upon applying the update.
206 --file <path>
208 A path to a file containing all the update details.
209 --requirements <Taskotron tasks>
211 A comma or space-separated list of required Taskotron tasks that
212 must pass for this update to reach stable.
213 bodhi updates edit [options] <update>
215 Edit an existing bodhi update, given an update id or an update
216 title. The edit subcommand supports the following options:
217 --addbuilds <builds>
219 Add a comma separated list of build nvr to this update.
220 --removebuilds <builds>
222 Remove a comma separated list of build nvr from this update.
223 --type [security | bugfix | enhancement | newpackage]
225 The type of the new update.
226 --notes <text>
228 The description of the update.
229 --notes-file <path>
231 A path to a file containing a description of the update.
232 --bugs <bugs>
234 A comma separated list of bugs to associate with this update.
235 --close-bugs
237 If given, this flag will cause bodhi to close the referenced
238 bugs automatically when the update reaches stable.
239 --request [testing | stable | upush]
241 The repository requested for this update.
242 --autokarma
244 Enable autokarma for this update.
245 --stable-karma <integer>
247 Configure the stable karma threshold for the given value.
248 --unstable-karma <integer>
250 Configure the unstable karma threshold for the given value.
251 --suggest [logout | reboot]
253 Suggest that the user logout or reboot upon applying the update.
254 --requirements <Taskotron tasks>
256 A comma or space-separated list of required Taskotron tasks that
257 must pass for this update to reach stable.
258 bodhi updates query [options]
260 Query the bodhi server for updates.
261 If the query returns only one update, a detailed view of the update
263 will be displayed.
264 If more than one update is returned, the command will display a list
266 showing the packages contained in the update, the update con‐
267 tent-type (rpm / module / …), the current status of the update
268 (pushed / testing / …) and the date of the last status change with
269 the number of days passed since. A leading * marks security updates.
270 The query subcommand supports the following options:
272 --updateid <id>
274 Query for the update given by id.
275 --title <title>
277 Query for the update given by title.
278 --alias <alias>
280 Query for the update given by alias.
281 --approved-since <timestamp>
283 Query for updates approved after the given timestamp.
284 --approved-before <timestamp>
286 Query for updates approved before the given timestamp.
287 --modified-since <timestamp>
289 Query for updates modified after the given timestamp.
290 --modified-before <timestamp>
292 Query for updates modified before the given timestamp.
293 --builds <builds>
295 Query for updates containing the given builds, given as a
296 comma-separated list.
297 --bugs <bugs>
299 Query for updates related to the given bugs, given as a
300 comma-separated list.
301 --content-type <content_type>
303 Query for updates of a given content type: either rpm, module,
304 or (in the future) container.
305 --critpath
307 Query for updates submitted for the critical path.
308 --mine
310 Show only your updates.
311 --packages <packages>
313 Query for updates related to the given packages, given as a
314 comma-separated list.
315 --pushed
317 Query for updates that have been pushed.
318 --pushed-since <timestamp>
320 Query for updates that have been pushed after the given time‐
321 stamp.
322 --pushed-before <timestamp>
324 Query for updates that have been pushed before the given time‐
325 stamp.
326 --releases <releases>
328 Query for updates related to a list of releases, given as a
329 comma-separated list.
330 --locked
332 Query for updates that are currently locked.
333 --request [testing | stable | unpush]
335 Query for updates marked with the given request type.
336 --severity [unspecified, urgent, high, medium, low]
338 Query for updates with a specific severity.
339 --submitted-since <timestamp>
341 Query for updates that were submitted since the given timestamp.
342 --submitted-before <timestamp>
344 Query for updates that were submitted before the given time‐
345 stamp.
346 --status [pending | testing | stable | obsolete | unpushed]
348 Filter by status.
349 --suggest [logout | reboot]
351 Filter for updates that suggest logout or reboot to the user.
352 --type [newpackage | security | bugfix | enhancement]
354 Filter by update type.
355 --user <username>
357 Filter for updates by a list of usernames, given as a comma-sep‐
358 arated list.
359 --rows <integer>
361 Limits number of results shown per page.
362 --page <integer>
364 Go to page number.
365 bodhi updates request [options] <update> <state>
367 Request that the given update be changed to the given state. update
368 should be given by update id, and state should be one of testing,
369 stable, unpush, obsolete, or revoke.
370 bodhi updates waive [options] <update> <comment>
372 Show or waive unsatisfied test requirements on an update.
373 The following options are supported:
375 --show
377 List the unsatisfied test requirements.
378 --test TEXT
380 Waive the test specified by name in TEXT. all can be used to
381 waive all unsatisfied tests.
382 --debug
384 Display debugging information.
385
387 The releases command allows users to manage update releases.
388 bodhi releases create [options]
390 The create command allows administrators to create new releases in
391 Bodhi:
392 --branch TEXT
394 The git branch that corresponds to this release (e.g., f29).
395 --candidate-tag TEXT
397 The Koji tag to use to search for update candidates (e.g.,
398 f29-updates-candidate).
399 --composed-by-bodhi, --not-composed-by-bodhi
401 The flag that indicates whether the release is composed by Bodhi
402 or not.
403 --dist-tag TEXT
405 The Koji dist tag for this release (e.g., f29).
406 --id-prefix TEXT
408 The release’s prefix (e.g., FEDORA).
409 --long-name TEXT
411 The long name of the release (e.g., Fedora 29).
412 --name TEXT
414 The name of the release (e.g., F29).
415 --override-tag TEXT
417 The Koji tag to use for buildroot overrides (e.g., f29-over‐
418 ride).
419 --password TEXT
421 The password to use when authenticating to Bodhi.
422 --pending-stable-tag TEXT
424 The Koji tag to use on updates that are marked stable (e.g.,
425 f29-updates-pending).
426 --pending-testing-tag TEXT
428 The Koji tag to use on updates that are pending testing (e.g.,
429 f29-updates-pending-testing).
430 --stable-tag TEXT
432 The Koji tag to use for stable updates (e.g., f29-updates).
433 --state [disabled|pending|current|archived]
435 The state of the release.
436 --testing-tag TEXT
438 The Koji tag to use for testing updates (e.g., f29-updates-test‐
439 ing).
440 --username TEXT
442 The username to use when authenticating to Bodhi.
443 --version TEXT
445 The version of the release (e.g., 29).
446 bodhi releases edit [options]
448 The edit command allows administrators to edit existing releases:
449 --branch TEXT
451 The git branch that corresponds to this release (e.g., f29).
452 --candidate-tag TEXT
454 The Koji tag to use to search for update candidates (e.g.,
455 f29-updates-candidate).
456 --composed-by-bodhi, --not-composed-by-bodhi
458 The flag that indicates whether the release is composed by Bodhi
459 or not.
460 --dist-tag TEXT
462 The Koji dist tag for this release (e.g., f29).
463 --id-prefix TEXT
465 The release’s prefix (e.g., FEDORA).
466 --long-name TEXT
468 The long name of the release (e.g., Fedora 29).
469 --name TEXT
471 The name of the release (e.g., F29).
472 --new-name
474 Change the release’s name to a new value (e.g., F29).
475 --override-tag TEXT
477 The Koji tag to use for buildroot overrides (e.g., f29-over‐
478 ride).
479 --password TEXT
481 The password to use when authenticating to Bodhi.
482 --pending-stable-tag TEXT
484 The Koji tag to use on updates that are marked stable (e.g.,
485 f29-updates-pending).
486 --pending-testing-tag TEXT
488 The Koji tag to use on updates that are pending testing (e.g.,
489 f29-updates-testing-pending).
490 --stable-tag TEXT
492 The Koji tag to use for stable updates (e.g., f29-updates).
493 --state [disabled|pending|current|archived]
495 The state of the release.
496 --testing-tag TEXT
498 The Koji tag to use for testing updates (e.g., f29-updates-test‐
499 ing).
500 --username TEXT
502 The username to use when authenticating to Bodhi.
503 --version TEXT
505 The version of the release (e.g., 29).
506 bodhi releases info RELEASE_NAME
508 The info command prints information about the given release.
509 bodhi releases list [options]
511 The list command prints list of releases.
512 --display-archived
514 Display full list, including archived releases.
515 --rows <integer>
517 Limits number of results shown per page.
518 --page <integer>
520 Go to page number.
521
523 Create a new update with multiple builds:
524 $ bodhi updates new --user bowlofeggs --type bugfix --notes "Fix permission issues during startup." --bugs 1393587 --close-bugs --request testing --autokarma --stable-karma 3 --unstable-karma -3 ejabberd-16.09-2.fc25,erlang-esip-1.0.8-1.fc25,erlang-fast_tls-1.0.7-1.fc25,erlang-fast_yaml-1.0.6-1.fc25,erlang-fast_xml-1.1.15-1.fc25,erlang-iconv-1.0.2-1.fc25,erlang-stringprep-1.0.6-1.fc25,erlang-stun-1.0.7-1.fc25
526
528 If you find bugs in bodhi (or in the man page), please feel free to
529 file a bug report or a pull request:
530 https://github.com/fedora-infra/bodhi
532 Bodhi’s documentation is available online:
534 https://bodhi.fedoraproject.org/docs
535
537 Randy Barlow, Luke Macken
538
540 2007-2019, Red Hat, Inc.
5414.0 Jun 18, 2019 BODHI(1)