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 --client-id <string>
20 Use the provided OpenID Connect client_id instead of the default
21 one. This is ignored if the --staging flag is set.
22 --debug
24 Some commands accept this flag to show extra debug information.
25 --help
27 Show help text and exit.
28 --id-provider <url>
30 Use the OpenID Connect provider at the given URL instead of the de‐
31 fault server. This can also be set with the BODHI_OPENID_PROVIDER
32 environment variable. This is ignored if the --staging flag is set.
33 --staging
35 Use the staging bodhi instance instead of the production instance.
36 --url <url>
38 Use the Bodhi server at the given URL instead of the default server.
39 This can also be set with the BODHI_URL environment variable. This
40 is ignored if the --staging flag is set.
41 --version
43 Show version and exit. Not accepted by subcommands.
44
46 There are four commands, composes, overrides, updates and releases.
47 They are described in more detail in their own sections below.
48 bodhi composes <subcommand> [options] [args]
50 Provides an interface to view composes. Supports subcommands list
51 and info, described below.
52 bodhi overrides <subcommand> [options] [args]
54 Provides commands to aid in management of build overrides. Supports
55 subcommands query and save, described below.
56 bodhi updates <subcommand> [options] [args]
58 Provides an interface to manage updates. Supports subcommands com‐
59 ment, download, new, query, and request, described below.
60 bodhi releases <subcommand> [options] [args]
62 Provides an interface to manage releases. Supports subcommands cre‐
63 ate, edit, info and list, described below.
64
66 The composes command allows users to view composes.
67 bodhi composes list [options]
69 The list subcommand allows you to see the current composes on the
70 Bodhi server. It supports the following options:
71 -v, --verbose
73 Print more detail about the composes.
74 bodhi composes info [options] RELEASE REQUEST
76 The info subcommand allows you to see the compose for release with
77 the given request.
78
80 The overrides command allows users to manage build overrides.
81 bodhi overrides query [options]
83 The query subcommand provides an interface for users to query the
84 bodhi server for existing overrides. The query subcommand supports
85 the following options:
86 --mine
88 Show only your overrides.
89 --active
91 Filter for only active overrides
92 --expired
94 Filter for only expired overrides
95 --packages <packagename>
97 Query for overrides related to the given packages, given as a
98 comma-separated list.
99 --releases <releases>
101 Query for overrides related to a list of releases, given as a
102 comma-separated list. <releases> is the release shortname, for
103 example: F26 or F26,F25, or a macro filter (__current__, __pend‐
104 ing__, __archived__) to include all releases in a certain sta‐
105 tus.
106 --builds <builds>
108 Query for overrides for a list of builds, given as a comma-sepa‐
109 rated list. <builds> is the build NVR, for example: core‐
110 bird-1.3-0.fc24
111 --user <username>
113 Filter for overrides by a list of usernames, given as a
114 comma-separated list.
115 --rows <integer>
117 Limits number of results shown per page.
118 --page <integer>
120 Go to page number.
121 bodhi overrides save [options] <nvr>
123 Save the build root given by <nvr> as a buildroot override. The save
124 subcommand supports the following options:
125 --duration <days>
127 The number of days the override should exist, given as an inte‐
128 ger.
129 --notes <text>
131 Notes on why this override is in place.
132 bodhi overrides edit [options] <nvr>
134 Edit the build root given by <nvr> as a buildroot override. The edit
135 subcommand supports the same options than the save command and also
136 the following option:
137 --expire
139 Force an override to the expired state.
140
142 The updates command allows users to interact with bodhi updates.
143 bodhi updates comment [options] <update> <text>
145 Leave the given text as a comment on a bodhi update. The comment
146 subcommand supports the following options:
147 --karma [+1 | 0 | -1]
149 The karma value you wish to contribute to the update.
150 bodhi updates download [options]
152 Download update(s) given by ID(s) or NVR(s). One of --updateid or
153 builds is required. The download subcommand supports the following
154 options:
155 --debuginfo
157 Include debuginfo packages when downloading.
158 --updateid <ids>
160 A comma-separated list of update IDs you would like to download.
161 --builds <nvrs>
163 A comma-separated list of NVRs that identify updates you would
164 like to download.
165 --arch <arch>
167 You can specify an architecture of packages to download. "all"
168 will download packages for all architectures. Omitting this op‐
169 tion will download packages for the architecture you are cur‐
170 rently running.
171 bodhi updates new [options] <builds_or_tag>
173 Create a new bodhi update containing the builds, given as a comma
174 separated list of NVRs. The new subcommand supports the following
175 options:
176 --type [security | bugfix | enhancement | newpackage]
178 The type of the new update.
179 --notes <text>
181 The description of the update.
182 --notes-file <path>
184 A path to a file containing a description of the update.
185 --bugs <bugs>
187 A comma separated list of bugs to associate with this update.
188 --close-bugs / --no-close-bugs
190 If given, this flag will cause bodhi to close the referenced
191 bugs automatically when the update reaches stable. When creating
192 a new update this is off by default.
193 --request [testing | stable | upush]
195 The repository requested for this update.
196 --autokarma / --no-autokarma
198 Enable or disable autokarma for this update. When creating a new
199 update this is off by default.
200 --autotime / --no-autotime
202 Enable autotime for this update. Automatically push the update
203 to stable based on the time spent in testing. When creating a
204 new update this is off by default.
205 --stable-karma <integer>
207 Configure the stable karma threshold for the given value.
208 --unstable-karma <integer>
210 Configure the unstable karma threshold for the given value.
211 --stable-days <integer>
213 Configure the number of days an update has to spend in testing
214 before being automatically pushed to stable.
215 --suggest [logout | reboot]
217 Suggest that the user logout or reboot upon applying the update.
218 --file <path>
220 A path to a file containing all the update details.
221 --requirements <Taskotron tasks>
223 A comma or space-separated list of required Taskotron tasks that
224 must pass for this update to reach stable.
225 --display-name <text>
227 The name of the update
228 --from-tag
230 If this flag is provided, <builds_or_tag> will be interpreted as
231 a Koji tag and expand to all latest builds in it. Only a single
232 tag can be provided.
233 bodhi updates edit [options] <update>
235 Edit an existing bodhi update, given an update id or an update ti‐
236 tle. The edit subcommand supports the following options:
237 --addbuilds <builds>
239 Add a comma separated list of build nvr to this update.
240 --removebuilds <builds>
242 Remove a comma separated list of build nvr from this update.
243 --type [security | bugfix | enhancement | newpackage]
245 The type of the new update.
246 --notes <text>
248 The description of the update.
249 --notes-file <path>
251 A path to a file containing a description of the update.
252 --bugs <bugs>
254 A comma separated list of bugs to associate with this update.
255 --close-bugs
257 If given, this flag will cause bodhi to close the referenced
258 bugs automatically when the update reaches stable.
259 --request [testing | stable | upush]
261 The repository requested for this update.
262 --autokarma
264 Enable autokarma for this update.
265 --stable-karma <integer>
267 Configure the stable karma threshold for the given value.
268 --unstable-karma <integer>
270 Configure the unstable karma threshold for the given value.
271 --suggest [logout | reboot]
273 Suggest that the user logout or reboot upon applying the update.
274 --requirements <Taskotron tasks>
276 A comma or space-separated list of required Taskotron tasks that
277 must pass for this update to reach stable.
278 --display-name <text>
280 The name of the update
281 --from-tag
283 If given, for updates that were created from a Koji tag, this
284 will update the builds to the latest ones in the tag.
285 bodhi updates query [options]
287 Query the bodhi server for updates.
288 If the query returns only one update, a detailed view of the update
290 will be displayed.
291 If more than one update is returned, the command will display a list
293 showing the packages contained in the update, the update con‐
294 tent-type (rpm / module / ...), the current status of the update
295 (pushed / testing / ...) and the date of the last status change with
296 the number of days passed since. A leading * marks security updates.
297 The query subcommand supports the following options:
299 --updateid <id>
301 Query for the update given by id.
302 --title <title>
304 Query for the update given by title.
305 --alias <alias>
307 Query for the update given by alias.
308 --approved-since <timestamp>
310 Query for updates approved after the given timestamp.
311 --approved-before <timestamp>
313 Query for updates approved before the given timestamp.
314 --modified-since <timestamp>
316 Query for updates modified after the given timestamp.
317 --modified-before <timestamp>
319 Query for updates modified before the given timestamp.
320 --builds <builds>
322 Query for updates containing the given builds, given as a
323 comma-separated list.
324 --bugs <bugs>
326 Query for updates related to the given bugs, given as a
327 comma-separated list.
328 --content-type <content_type>
330 Query for updates of a given content type: either rpm, module,
331 or (in the future) container.
332 --critpath
334 Query for updates submitted for the critical path.
335 --from-side-tag
337 Query for updates created from a side-tag.
338 --not-from-side-tag
340 Query for updates not created from a side-tag.
341 --gating [passed | failed | ignored | waiting | running | queued |
343 greenwave_failed]
344 Query for updates based on test gating status.
345 --mine
347 Show only your updates.
348 --packages <packages>
350 Query for updates related to the given packages, given as a
351 comma-separated list.
352 --pushed
354 Query for updates that have been pushed.
355 --pushed-since <timestamp>
357 Query for updates that have been pushed after the given time‐
358 stamp.
359 --pushed-before <timestamp>
361 Query for updates that have been pushed before the given time‐
362 stamp.
363 --releases <releases>
365 Query for updates related to a list of releases, given as a
366 comma-separated list. It is possible to use the macro filters
367 __current__, __pending__ and __archived__ to include all re‐
368 leases in a certain status.
369 --locked
371 Query for updates that are currently locked.
372 --request [testing | stable | unpush]
374 Query for updates marked with the given request type.
375 --severity [unspecified, urgent, high, medium, low]
377 Query for updates with a specific severity.
378 --submitted-since <timestamp>
380 Query for updates that were submitted since the given timestamp.
381 --submitted-before <timestamp>
383 Query for updates that were submitted before the given time‐
384 stamp.
385 --status [pending | testing | stable | obsolete | unpushed]
387 Filter by status.
388 --suggest [logout | reboot]
390 Filter for updates that suggest logout or reboot to the user.
391 --type [newpackage | security | bugfix | enhancement]
393 Filter by update type.
394 --user <username>
396 Filter for updates by a list of usernames, given as a comma-sep‐
397 arated list.
398 --rows <integer>
400 Limits number of results shown per page.
401 --page <integer>
403 Go to page number.
404 bodhi updates request [options] <update> <state>
406 Request that the given update be changed to the given state. update
407 should be given by update id, and state should be one of testing,
408 stable, unpush, obsolete, or revoke.
409 bodhi updates waive [options] <update> <comment>
411 Show or waive unsatisfied test requirements on an update.
412 The following options are supported:
414 --show
416 List the unsatisfied test requirements.
417 --test TEXT
419 Waive the test specified by name in TEXT. all can be used to
420 waive all unsatisfied tests.
421 --debug
423 Display debugging information.
424 bodhi updates trigger-tests [options] <update>
426 Trigger tests for an update. This update must be in testing state.
427
429 The releases command allows users to manage update releases.
430 bodhi releases create [options]
432 The create command allows administrators to create new releases in
433 Bodhi:
434 --branch TEXT
436 The git branch that corresponds to this release (e.g., f29).
437 --candidate-tag TEXT
439 The Koji tag to use to search for update candidates (e.g.,
440 f29-updates-candidate).
441 --composed-by-bodhi, --not-composed-by-bodhi
443 The flag that indicates whether the release is composed by Bodhi
444 or not.
445 --dist-tag TEXT
447 The Koji dist tag for this release (e.g., f29).
448 --id-prefix TEXT
450 The release's prefix (e.g., FEDORA).
451 --long-name TEXT
453 The long name of the release (e.g., Fedora 29).
454 --name TEXT
456 The name of the release (e.g., F29).
457 --override-tag TEXT
459 The Koji tag to use for buildroot overrides (e.g., f29-over‐
460 ride).
461 --package-manager [unspecified|dnf|yum]
463 The package manager used by this release. If not specified it
464 defaults to 'unspecified'.
465 --pending-stable-tag TEXT
467 The Koji tag to use on updates that are marked stable (e.g.,
468 f29-updates-pending).
469 --pending-testing-tag TEXT
471 The Koji tag to use on updates that are pending testing (e.g.,
472 f29-updates-pending-testing).
473 --stable-tag TEXT
475 The Koji tag to use for stable updates (e.g., f29-updates).
476 --state [disabled|pending|frozen|current|archived]
478 The state of the release.
479 --testing-repository TEXT
481 The name of the testing repository used to test updates. Not re‐
482 quired.
483 --testing-tag TEXT
485 The Koji tag to use for testing updates (e.g., f29-updates-test‐
486 ing).
487 --version TEXT
489 The version of the release (e.g., 29).
490 bodhi releases edit [options]
492 The edit command allows administrators to edit existing releases:
493 --branch TEXT
495 The git branch that corresponds to this release (e.g., f29).
496 --candidate-tag TEXT
498 The Koji tag to use to search for update candidates (e.g.,
499 f29-updates-candidate).
500 --composed-by-bodhi, --not-composed-by-bodhi
502 The flag that indicates whether the release is composed by Bodhi
503 or not.
504 --dist-tag TEXT
506 The Koji dist tag for this release (e.g., f29).
507 --id-prefix TEXT
509 The release's prefix (e.g., FEDORA).
510 --long-name TEXT
512 The long name of the release (e.g., Fedora 29).
513 --name TEXT
515 The name of the release (e.g., F29).
516 --new-name
518 Change the release's name to a new value (e.g., F29).
519 --override-tag TEXT
521 The Koji tag to use for buildroot overrides (e.g., f29-over‐
522 ride).
523 --package-manager [unspecified|dnf|yum]
525 The package manager used by this release. If not specified it
526 defaults to 'unspecified'.
527 --pending-stable-tag TEXT
529 The Koji tag to use on updates that are marked stable (e.g.,
530 f29-updates-pending).
531 --pending-testing-tag TEXT
533 The Koji tag to use on updates that are pending testing (e.g.,
534 f29-updates-testing-pending).
535 --stable-tag TEXT
537 The Koji tag to use for stable updates (e.g., f29-updates).
538 --state [disabled|pending|frozen|current|archived]
540 The state of the release.
541 --testing-repository TEXT
543 The name of the testing repository used to test updates. Not re‐
544 quired.
545 --testing-tag TEXT
547 The Koji tag to use for testing updates (e.g., f29-updates-test‐
548 ing).
549 --version TEXT
551 The version of the release (e.g., 29).
552 bodhi releases info RELEASE_NAME
554 The info command prints information about the given release.
555 bodhi releases list [options]
557 The list command prints list of releases.
558 --display-archived
560 Display full list, including archived releases.
561 --rows <integer>
563 Limits number of results shown per page.
564 --page <integer>
566 Go to page number.
567
569 Create a new update with multiple builds:
570 $ 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
572
574 If you find bugs in bodhi (or in the man page), please feel free to
575 file a bug report or a pull request:
576 https://github.com/fedora-infra/bodhi
578 Bodhi's documentation is available online:
580 https://fedora-infra.github.io/bodhi
581
583 Randy Barlow, Luke Macken
584
586 2007-2022, Red Hat, Inc.
587 Jul 15, 2022 BODHI(1)