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_or_tag>
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 --autotime
199 Enable autotime for this update. Automatically push the update
200 to stable based on the time spent in testing.
201 --stable-karma <integer>
203 Configure the stable karma threshold for the given value.
204 --unstable-karma <integer>
206 Configure the unstable karma threshold for the given value.
207 --stable-days <integer>
209 Configure the number of days an update has to spend in testing
210 before being automatically pushed to stable.
211 --suggest [logout | reboot]
213 Suggest that the user logout or reboot upon applying the update.
214 --file <path>
216 A path to a file containing all the update details.
217 --requirements <Taskotron tasks>
219 A comma or space-separated list of required Taskotron tasks that
220 must pass for this update to reach stable.
221 --display-name <text>
223 The name of the update
224 --from-tag
226 If this flag is provided, <builds_or_tag> will be interpreted as
227 a Koji tag and expand to all latest builds in it. Only a single
228 tag can be provided.
229 bodhi updates edit [options] <update>
231 Edit an existing bodhi update, given an update id or an update
232 title. The edit subcommand supports the following options:
233 --addbuilds <builds>
235 Add a comma separated list of build nvr to this update.
236 --removebuilds <builds>
238 Remove a comma separated list of build nvr from this update.
239 --type [security | bugfix | enhancement | newpackage]
241 The type of the new update.
242 --notes <text>
244 The description of the update.
245 --notes-file <path>
247 A path to a file containing a description of the update.
248 --bugs <bugs>
250 A comma separated list of bugs to associate with this update.
251 --close-bugs
253 If given, this flag will cause bodhi to close the referenced
254 bugs automatically when the update reaches stable.
255 --request [testing | stable | upush]
257 The repository requested for this update.
258 --autokarma
260 Enable autokarma for this update.
261 --stable-karma <integer>
263 Configure the stable karma threshold for the given value.
264 --unstable-karma <integer>
266 Configure the unstable karma threshold for the given value.
267 --suggest [logout | reboot]
269 Suggest that the user logout or reboot upon applying the update.
270 --requirements <Taskotron tasks>
272 A comma or space-separated list of required Taskotron tasks that
273 must pass for this update to reach stable.
274 --display-name <text>
276 The name of the update
277 --from-tag
279 If given, for updates that were created from a Koji tag, this
280 will update the builds to the latest ones in the tag.
281 bodhi updates query [options]
283 Query the bodhi server for updates.
284 If the query returns only one update, a detailed view of the update
286 will be displayed.
287 If more than one update is returned, the command will display a list
289 showing the packages contained in the update, the update con‐
290 tent-type (rpm / module / …), the current status of the update
291 (pushed / testing / …) and the date of the last status change with
292 the number of days passed since. A leading * marks security updates.
293 The query subcommand supports the following options:
295 --updateid <id>
297 Query for the update given by id.
298 --title <title>
300 Query for the update given by title.
301 --alias <alias>
303 Query for the update given by alias.
304 --approved-since <timestamp>
306 Query for updates approved after the given timestamp.
307 --approved-before <timestamp>
309 Query for updates approved before the given timestamp.
310 --modified-since <timestamp>
312 Query for updates modified after the given timestamp.
313 --modified-before <timestamp>
315 Query for updates modified before the given timestamp.
316 --builds <builds>
318 Query for updates containing the given builds, given as a
319 comma-separated list.
320 --bugs <bugs>
322 Query for updates related to the given bugs, given as a
323 comma-separated list.
324 --content-type <content_type>
326 Query for updates of a given content type: either rpm, module,
327 or (in the future) container.
328 --critpath
330 Query for updates submitted for the critical path.
331 --mine
333 Show only your updates.
334 --packages <packages>
336 Query for updates related to the given packages, given as a
337 comma-separated list.
338 --pushed
340 Query for updates that have been pushed.
341 --pushed-since <timestamp>
343 Query for updates that have been pushed after the given time‐
344 stamp.
345 --pushed-before <timestamp>
347 Query for updates that have been pushed before the given time‐
348 stamp.
349 --releases <releases>
351 Query for updates related to a list of releases, given as a
352 comma-separated list.
353 --locked
355 Query for updates that are currently locked.
356 --request [testing | stable | unpush]
358 Query for updates marked with the given request type.
359 --severity [unspecified, urgent, high, medium, low]
361 Query for updates with a specific severity.
362 --submitted-since <timestamp>
364 Query for updates that were submitted since the given timestamp.
365 --submitted-before <timestamp>
367 Query for updates that were submitted before the given time‐
368 stamp.
369 --status [pending | testing | stable | obsolete | unpushed]
371 Filter by status.
372 --suggest [logout | reboot]
374 Filter for updates that suggest logout or reboot to the user.
375 --type [newpackage | security | bugfix | enhancement]
377 Filter by update type.
378 --user <username>
380 Filter for updates by a list of usernames, given as a comma-sep‐
381 arated list.
382 --rows <integer>
384 Limits number of results shown per page.
385 --page <integer>
387 Go to page number.
388 bodhi updates request [options] <update> <state>
390 Request that the given update be changed to the given state. update
391 should be given by update id, and state should be one of testing,
392 stable, unpush, obsolete, or revoke.
393 bodhi updates waive [options] <update> <comment>
395 Show or waive unsatisfied test requirements on an update.
396 The following options are supported:
398 --show
400 List the unsatisfied test requirements.
401 --test TEXT
403 Waive the test specified by name in TEXT. all can be used to
404 waive all unsatisfied tests.
405 --debug
407 Display debugging information.
408 bodhi updates trigger-tests [options] <update>
410 Trigger tests for an update. This update must be in testing state.
411
413 The releases command allows users to manage update releases.
414 bodhi releases create [options]
416 The create command allows administrators to create new releases in
417 Bodhi:
418 --branch TEXT
420 The git branch that corresponds to this release (e.g., f29).
421 --candidate-tag TEXT
423 The Koji tag to use to search for update candidates (e.g.,
424 f29-updates-candidate).
425 --composed-by-bodhi, --not-composed-by-bodhi
427 The flag that indicates whether the release is composed by Bodhi
428 or not.
429 --dist-tag TEXT
431 The Koji dist tag for this release (e.g., f29).
432 --id-prefix TEXT
434 The release’s prefix (e.g., FEDORA).
435 --long-name TEXT
437 The long name of the release (e.g., Fedora 29).
438 --name TEXT
440 The name of the release (e.g., F29).
441 --override-tag TEXT
443 The Koji tag to use for buildroot overrides (e.g., f29-over‐
444 ride).
445 --package-manager [unspecified|dnf|yum]
447 The package manager used by this release. If not specified it
448 defaults to ‘unspecified’.
449 --password TEXT
451 The password to use when authenticating to Bodhi.
452 --pending-stable-tag TEXT
454 The Koji tag to use on updates that are marked stable (e.g.,
455 f29-updates-pending).
456 --pending-testing-tag TEXT
458 The Koji tag to use on updates that are pending testing (e.g.,
459 f29-updates-pending-testing).
460 --stable-tag TEXT
462 The Koji tag to use for stable updates (e.g., f29-updates).
463 --state [disabled|pending|frozen|current|archived]
465 The state of the release.
466 --testing-repository TEXT
468 The name of the testing repository used to test updates. Not
469 required.
470 --testing-tag TEXT
472 The Koji tag to use for testing updates (e.g., f29-updates-test‐
473 ing).
474 --username TEXT
476 The username to use when authenticating to Bodhi.
477 --version TEXT
479 The version of the release (e.g., 29).
480 bodhi releases edit [options]
482 The edit command allows administrators to edit existing releases:
483 --branch TEXT
485 The git branch that corresponds to this release (e.g., f29).
486 --candidate-tag TEXT
488 The Koji tag to use to search for update candidates (e.g.,
489 f29-updates-candidate).
490 --composed-by-bodhi, --not-composed-by-bodhi
492 The flag that indicates whether the release is composed by Bodhi
493 or not.
494 --dist-tag TEXT
496 The Koji dist tag for this release (e.g., f29).
497 --id-prefix TEXT
499 The release’s prefix (e.g., FEDORA).
500 --long-name TEXT
502 The long name of the release (e.g., Fedora 29).
503 --name TEXT
505 The name of the release (e.g., F29).
506 --new-name
508 Change the release’s name to a new value (e.g., F29).
509 --override-tag TEXT
511 The Koji tag to use for buildroot overrides (e.g., f29-over‐
512 ride).
513 --package-manager [unspecified|dnf|yum]
515 The package manager used by this release. If not specified it
516 defaults to ‘unspecified’.
517 --password TEXT
519 The password to use when authenticating to Bodhi.
520 --pending-stable-tag TEXT
522 The Koji tag to use on updates that are marked stable (e.g.,
523 f29-updates-pending).
524 --pending-testing-tag TEXT
526 The Koji tag to use on updates that are pending testing (e.g.,
527 f29-updates-testing-pending).
528 --stable-tag TEXT
530 The Koji tag to use for stable updates (e.g., f29-updates).
531 --state [disabled|pending|frozen|current|archived]
533 The state of the release.
534 --testing-repository TEXT
536 The name of the testing repository used to test updates. Not
537 required.
538 --testing-tag TEXT
540 The Koji tag to use for testing updates (e.g., f29-updates-test‐
541 ing).
542 --username TEXT
544 The username to use when authenticating to Bodhi.
545 --version TEXT
547 The version of the release (e.g., 29).
548 bodhi releases info RELEASE_NAME
550 The info command prints information about the given release.
551 bodhi releases list [options]
553 The list command prints list of releases.
554 --display-archived
556 Display full list, including archived releases.
557 --rows <integer>
559 Limits number of results shown per page.
560 --page <integer>
562 Go to page number.
563
565 Create a new update with multiple builds:
566 $ 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
568
570 If you find bugs in bodhi (or in the man page), please feel free to
571 file a bug report or a pull request:
572 https://github.com/fedora-infra/bodhi
574 Bodhi’s documentation is available online:
576 https://bodhi.fedoraproject.org/docs
577
579 Randy Barlow, Luke Macken
580
582 2007-2020, Red Hat, Inc.
5835.1 Jan 30, 2020 BODHI(1)