Obviously, replace `PATH_TO_SRPM` with the full path
(not URL)
to your approved SRPM,
and `XXXXXX` with the package review bug number.

If your package is using _autochangelog_, writing the bug number as specified
will make the Fedora update system automatically close the bug when your package is
submitted to Rawhide stable repository.

This imports into, commits, and builds only the *main*
(xref:releases::rawhide.adoc[Rawhide])
branch.

If the push fails with this kind of message:

Then you don't have the necessary rights to modify that package branch.
View `\https://src.fedoraproject.org/rpms/PACKAGE_NAME` to request those rights.

For more information on using the Fedora package maintenance system,
see the xref:Package_Maintenance_Guide.adoc[Package maintenance guide].

[#update_your_branches]
== Update Your Branches (if desired)

Branches are `f#` (formerly `F-#` and before that `FC-#`), `main`, etc. So `f` is the branch for Fedora.

To switch to a branch first:

(e.g. `f{MAJOROSVER}`)

Merge the initial commit from main (Rawhide),
creating an identical commit in the branch:

Push the changes to the server:

Build the package:

If there is another branch to work with
repeat _To switch to a branch_
and import and commit to each branch.

If everything goes well,
it should queue up your branch for building,
the package will cleanly build,
and you're done!

If it fails to build,
the build system will send you an email
to report the failure
and show you to the logs.
Commit any needed changes to git,
bump the SPEC release number,
and request a new build.

[#submit_package_as_update_in_bodhi]
=== Submit Package as Update in Bodhi

The Fedora update system called https://bodhi.fedoraproject.org[Bodhi] is used for pushing updates, classifying packages etc. You do not need to submit updates for Rawhide (main) manually because these are automatically created for you when the build completes. For all other branches, you must manually push updates for all builds that you would like to make available to users.

You can push an update using Bodhi via the command line using this in each branch:

It is often easier to complete builds for all your branches
and then push a single update using the https://bodhi.fedoraproject.org/updates/new[Bodhi web interface].
Bodhi is smart enough to split your update into individual updates,
one for each Fedora release branch.

You can also select multiple builds from different packages
to include in a single update using the web interface.
This is useful when you would like to push linked builds,
for example: an application package and its dependencies
that are necessary for it to run correctly.

Please see the xref:Package_Update_Guide.adoc[Package Update Guide] for more details.

[#make_the_package_available_in_comps_files]
== Make the package available in "comps" files

If appropriate for the package, make it available in "comps" files so that it can be selected during installation and included in dnf package group operations. See https://fedoraproject.org/wiki/How_to_use_and_edit_comps.xml_for_package_groups?rd=PackageMaintainers/CompsXml[How to use and edit comps.xml for package groups] for more info.

[#watch_for_updates]
=== Watch for updates

Fedora has the infrastructure available for monitoring new upstream releases of the software you are packaging. Refer to xref:Upstream_Release_Monitoring.adoc[Upstream Release Monitoring] for more details.