1BODHI(1) bodhi BODHI(1)
2
3
4
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
19 --debug
20 Some commands accept this flag to show extra debug information.
21
22 --help
23 Show help text and exit.
24
25 --password <text>
26 A password to authenticate as the user given by --user.
27
28 --staging
29 Use the staging bodhi instance instead of the production instance.
30
31 --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
36 --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
43 --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
50 bodhi composes <subcommand> [options] [args]
51 Provides an interface to view composes. Supports subcommands list
52 and info, described below.
53
54 bodhi overrides <subcommand> [options] [args]
55 Provides commands to aid in management of build overrides. Supports
56 subcommands query and save, described below.
57
58 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
62 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
69 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
73 -v, --verbose
74 Print more detail about the composes.
75
76 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
83 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
88 --mine
89 Show only your overrides.
90
91 --active
92 Filter for only active overrides
93
94 --expired
95 Filter for only expired overrides
96
97 --packages <packagename>
98 Query for overrides related to the given packages, given as a
99 comma-separated list.
100
101 --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
106 --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
111 --user <username>
112 Filter for overrides by a list of usernames, given as a
113 comma-separated list.
114
115 --rows <integer>
116 Limits number of results shown per page.
117
118 --page <integer>
119 Go to page number.
120
121 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
125 --duration <days>
126 The number of days the override should exist, given as an inte‐
127 ger.
128
129 --notes <text>
130 Notes on why this override is in place.
131
132 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
137 --expire
138 Force an override to the expired state.
139
141 The updates command allows users to interact with bodhi updates.
142
143 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
147 --karma [+1 | 0 | -1]
148 The karma value you wish to contribute to the update.
149
150 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
155 --debuginfo
156 Include debuginfo packages when downloading.
157
158 --updateid <ids>
159 A comma-separated list of update IDs you would like to download.
160
161 --builds <nvrs>
162 A comma-separated list of NVRs that identify updates you would
163 like to download.
164
165 --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
171 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
176 --type [security | bugfix | enhancement | newpackage]
177 The type of the new update.
178
179 --notes <text>
180 The description of the update.
181
182 --notes-file <path>
183 A path to a file containing a description of the update.
184
185 --bugs <bugs>
186 A comma separated list of bugs to associate with this update.
187
188 --close-bugs
189 If given, this flag will cause bodhi to close the referenced
190 bugs automatically when the update reaches stable.
191
192 --request [testing | stable | upush]
193 The repository requested for this update.
194
195 --autokarma
196 Enable autokarma for this update.
197
198 --autotime
199 Enable autotime for this update. Automatically push the update
200 to stable based on the time spent in testing.
201
202 --stable-karma <integer>
203 Configure the stable karma threshold for the given value.
204
205 --unstable-karma <integer>
206 Configure the unstable karma threshold for the given value.
207
208 --stable-days <integer>
209 Configure the number of days an update has to spend in testing
210 before being automatically pushed to stable.
211
212 --suggest [logout | reboot]
213 Suggest that the user logout or reboot upon applying the update.
214
215 --file <path>
216 A path to a file containing all the update details.
217
218 --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
222 --display-name <text>
223 The name of the update
224
225 bodhi updates edit [options] <update>
226 Edit an existing bodhi update, given an update id or an update
227 title. The edit subcommand supports the following options:
228
229 --addbuilds <builds>
230 Add a comma separated list of build nvr to this update.
231
232 --removebuilds <builds>
233 Remove a comma separated list of build nvr from this update.
234
235 --type [security | bugfix | enhancement | newpackage]
236 The type of the new update.
237
238 --notes <text>
239 The description of the update.
240
241 --notes-file <path>
242 A path to a file containing a description of the update.
243
244 --bugs <bugs>
245 A comma separated list of bugs to associate with this update.
246
247 --close-bugs
248 If given, this flag will cause bodhi to close the referenced
249 bugs automatically when the update reaches stable.
250
251 --request [testing | stable | upush]
252 The repository requested for this update.
253
254 --autokarma
255 Enable autokarma for this update.
256
257 --stable-karma <integer>
258 Configure the stable karma threshold for the given value.
259
260 --unstable-karma <integer>
261 Configure the unstable karma threshold for the given value.
262
263 --suggest [logout | reboot]
264 Suggest that the user logout or reboot upon applying the update.
265
266 --requirements <Taskotron tasks>
267 A comma or space-separated list of required Taskotron tasks that
268 must pass for this update to reach stable.
269
270 --display-name <text>
271 The name of the update
272
273 bodhi updates query [options]
274 Query the bodhi server for updates.
275
276 If the query returns only one update, a detailed view of the update
277 will be displayed.
278
279 If more than one update is returned, the command will display a list
280 showing the packages contained in the update, the update con‐
281 tent-type (rpm / module / …), the current status of the update
282 (pushed / testing / …) and the date of the last status change with
283 the number of days passed since. A leading * marks security updates.
284
285 The query subcommand supports the following options:
286
287 --updateid <id>
288 Query for the update given by id.
289
290 --title <title>
291 Query for the update given by title.
292
293 --alias <alias>
294 Query for the update given by alias.
295
296 --approved-since <timestamp>
297 Query for updates approved after the given timestamp.
298
299 --approved-before <timestamp>
300 Query for updates approved before the given timestamp.
301
302 --modified-since <timestamp>
303 Query for updates modified after the given timestamp.
304
305 --modified-before <timestamp>
306 Query for updates modified before the given timestamp.
307
308 --builds <builds>
309 Query for updates containing the given builds, given as a
310 comma-separated list.
311
312 --bugs <bugs>
313 Query for updates related to the given bugs, given as a
314 comma-separated list.
315
316 --content-type <content_type>
317 Query for updates of a given content type: either rpm, module,
318 or (in the future) container.
319
320 --critpath
321 Query for updates submitted for the critical path.
322
323 --mine
324 Show only your updates.
325
326 --packages <packages>
327 Query for updates related to the given packages, given as a
328 comma-separated list.
329
330 --pushed
331 Query for updates that have been pushed.
332
333 --pushed-since <timestamp>
334 Query for updates that have been pushed after the given time‐
335 stamp.
336
337 --pushed-before <timestamp>
338 Query for updates that have been pushed before the given time‐
339 stamp.
340
341 --releases <releases>
342 Query for updates related to a list of releases, given as a
343 comma-separated list.
344
345 --locked
346 Query for updates that are currently locked.
347
348 --request [testing | stable | unpush]
349 Query for updates marked with the given request type.
350
351 --severity [unspecified, urgent, high, medium, low]
352 Query for updates with a specific severity.
353
354 --submitted-since <timestamp>
355 Query for updates that were submitted since the given timestamp.
356
357 --submitted-before <timestamp>
358 Query for updates that were submitted before the given time‐
359 stamp.
360
361 --status [pending | testing | stable | obsolete | unpushed]
362 Filter by status.
363
364 --suggest [logout | reboot]
365 Filter for updates that suggest logout or reboot to the user.
366
367 --type [newpackage | security | bugfix | enhancement]
368 Filter by update type.
369
370 --user <username>
371 Filter for updates by a list of usernames, given as a comma-sep‐
372 arated list.
373
374 --rows <integer>
375 Limits number of results shown per page.
376
377 --page <integer>
378 Go to page number.
379
380 bodhi updates request [options] <update> <state>
381 Request that the given update be changed to the given state. update
382 should be given by update id, and state should be one of testing,
383 stable, unpush, obsolete, or revoke.
384
385 bodhi updates waive [options] <update> <comment>
386 Show or waive unsatisfied test requirements on an update.
387
388 The following options are supported:
389
390 --show
391 List the unsatisfied test requirements.
392
393 --test TEXT
394 Waive the test specified by name in TEXT. all can be used to
395 waive all unsatisfied tests.
396
397 --debug
398 Display debugging information.
399
401 The releases command allows users to manage update releases.
402
403 bodhi releases create [options]
404 The create command allows administrators to create new releases in
405 Bodhi:
406
407 --branch TEXT
408 The git branch that corresponds to this release (e.g., f29).
409
410 --candidate-tag TEXT
411 The Koji tag to use to search for update candidates (e.g.,
412 f29-updates-candidate).
413
414 --composed-by-bodhi, --not-composed-by-bodhi
415 The flag that indicates whether the release is composed by Bodhi
416 or not.
417
418 --dist-tag TEXT
419 The Koji dist tag for this release (e.g., f29).
420
421 --id-prefix TEXT
422 The release’s prefix (e.g., FEDORA).
423
424 --long-name TEXT
425 The long name of the release (e.g., Fedora 29).
426
427 --name TEXT
428 The name of the release (e.g., F29).
429
430 --override-tag TEXT
431 The Koji tag to use for buildroot overrides (e.g., f29-over‐
432 ride).
433
434 --package-manager [unspecified|dnf|yum]
435 The package manager used by this release. If not specified it
436 defaults to ‘unspecified’.
437
438 --password TEXT
439 The password to use when authenticating to Bodhi.
440
441 --pending-stable-tag TEXT
442 The Koji tag to use on updates that are marked stable (e.g.,
443 f29-updates-pending).
444
445 --pending-testing-tag TEXT
446 The Koji tag to use on updates that are pending testing (e.g.,
447 f29-updates-pending-testing).
448
449 --stable-tag TEXT
450 The Koji tag to use for stable updates (e.g., f29-updates).
451
452 --state [disabled|pending|current|archived]
453 The state of the release.
454
455 --testing-repository TEXT
456 The name of the testing repository used to test updates. Not
457 required.
458
459 --testing-tag TEXT
460 The Koji tag to use for testing updates (e.g., f29-updates-test‐
461 ing).
462
463 --username TEXT
464 The username to use when authenticating to Bodhi.
465
466 --version TEXT
467 The version of the release (e.g., 29).
468
469 bodhi releases edit [options]
470 The edit command allows administrators to edit existing releases:
471
472 --branch TEXT
473 The git branch that corresponds to this release (e.g., f29).
474
475 --candidate-tag TEXT
476 The Koji tag to use to search for update candidates (e.g.,
477 f29-updates-candidate).
478
479 --composed-by-bodhi, --not-composed-by-bodhi
480 The flag that indicates whether the release is composed by Bodhi
481 or not.
482
483 --dist-tag TEXT
484 The Koji dist tag for this release (e.g., f29).
485
486 --id-prefix TEXT
487 The release’s prefix (e.g., FEDORA).
488
489 --long-name TEXT
490 The long name of the release (e.g., Fedora 29).
491
492 --name TEXT
493 The name of the release (e.g., F29).
494
495 --new-name
496 Change the release’s name to a new value (e.g., F29).
497
498 --override-tag TEXT
499 The Koji tag to use for buildroot overrides (e.g., f29-over‐
500 ride).
501
502 --password TEXT
503 The password to use when authenticating to Bodhi.
504
505 --pending-stable-tag TEXT
506 The Koji tag to use on updates that are marked stable (e.g.,
507 f29-updates-pending).
508
509 --pending-testing-tag TEXT
510 The Koji tag to use on updates that are pending testing (e.g.,
511 f29-updates-testing-pending).
512
513 --stable-tag TEXT
514 The Koji tag to use for stable updates (e.g., f29-updates).
515
516 --state [disabled|pending|current|archived]
517 The state of the release.
518
519 --testing-tag TEXT
520 The Koji tag to use for testing updates (e.g., f29-updates-test‐
521 ing).
522
523 --username TEXT
524 The username to use when authenticating to Bodhi.
525
526 --version TEXT
527 The version of the release (e.g., 29).
528
529 bodhi releases info RELEASE_NAME
530 The info command prints information about the given release.
531
532 bodhi releases list [options]
533 The list command prints list of releases.
534
535 --display-archived
536 Display full list, including archived releases.
537
538 --rows <integer>
539 Limits number of results shown per page.
540
541 --page <integer>
542 Go to page number.
543
545 Create a new update with multiple builds:
546
547 $ 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
548
550 If you find bugs in bodhi (or in the man page), please feel free to
551 file a bug report or a pull request:
552
553 https://github.com/fedora-infra/bodhi
554
555 Bodhi’s documentation is available online:
556 https://bodhi.fedoraproject.org/docs
557
559 Randy Barlow, Luke Macken
560
562 2007-2019, Red Hat, Inc.
563
564
565
566
5674.1 Jul 25, 2019 BODHI(1)