From Fedora Project Wiki
(this is not true: man page says default duration is 3 days)
Line 8: Line 8:


== Submitting a new override ==
== Submitting a new override ==
{{admon/note|Auto expiration|If you do not specify a 'duration', which is the number of days you wish for it to be active, your override will automatically be expired when your update gets pushed to the 'stable' repository (or gets deleted/unpushed/obsoleted).}}


https://admin.fedoraproject.org/updates/override/new
https://admin.fedoraproject.org/updates/override/new

Revision as of 13:40, 31 May 2013

Using Bodhi to manage Koji Buildroot Overrides

This document describes how to manage your Koji BuildRoot Overrides using Bodhi. Each section contains URLs for performing actions via the web and commands for doing it from the console.

Idea.png
Legacy method
Legacy method/backup plan: submit releng ticket: https://fedorahosted.org/rel-eng/newticket

Submitting a new override

https://admin.fedoraproject.org/updates/override/new

    bodhi --buildroot-override=<name-version-release> --duration=5 --notes="Useful details."

Viewing your own overrides

https://admin.fedoraproject.org/updates/override/list?mine=True

    bodhi --my-overrides [--show-expired]

Viewing all overrides

https://admin.fedoraproject.org/updates/override/list

    bodhi --list-overrides [--show-expired]

Manually expiring your buildroot override

https://admin.fedoraproject.org/updates/override/expire/<name-version-release>

    bodhi --expire-override=<name-version-release>

Extending your duration or editing override notes

https://admin.fedoraproject.org/updates/override/edit/<name-version-release>

    bodhi --edit-override=<name-version-release> --duration=10 --notes="Oh hai"