New Package Process for Existing Contributors

You should make sure that it is a new package. A list of existing packages in Fedora Packages is here: https://src.fedoraproject.org/projects/rpms/*

Some information on how to create an RPM package is in Packaging Tutorial.

Make sure that your package meets the Packaging Guidelines and Package Naming Guidelines

Be aware of forbidden items and Package Review Guidelines. They will be used during the package review.

If you have already got a Fedora Account then you can use your storage at https://fedorapeople.org for this.

Make sure you put the name of the package in the Review Summary field, along with a very brief summary of what it is

Make sure that you put the URL paths for the SPEC file and the SRPM file in the Review Description

Put a description of your package (usually, this can be the same thing as what you put in the spec %description) in Review Description

The review process is described in detail in Package Review Guidelines.

Make sure the reviewer is the Assignee in your Bugzilla ticket.

Request a distgit repository with fedpkg request-repo PACKAGE-NAME BUGZILLA-TICKET-NUMBER. (Package Maintenance Guide has more information about fedpkg.) You might need to get a pagure-API-token before being able to successfully request the repo.

When the repo is created, it only contains the rawhide branch. If you want to bring the package to other Fedora releases, see Requesting branches.

First fkinit -u username

Then you can import the approved SRPM into the rawhide branch by running fedpkg import libfoo-x.x.x.src.rpm; git commit -m "Initial import (fedora#nnnnnn)." (where nnnnnn is your Bugzilla package review bug number). If your package is using autochangelog, writing the bug number as specified will make Bodhi automatically close the bug when your package is submitted to Rawhide stable repository.

Obviously, replace libfoo-x.x.x.src.rpm with the full path to your approved SRPM.

You should see it upload the sources, and finish successfully. If you didn’t set up ssh-agent it will ask often for your ssh-key passphrase. This is normal.

Now run git push to get the final versions in your rawhide branch.

The quickest way to do this is to use fedpkg switch-branch BRANCH to switch the branch (where BRANCH can be f13 and so on).

Now you can git merge rawhide. This will get .spec file, .gitignore and source file together with any patches and other files from the rawhide branch and create an identical commit.

Previous step already created commit for you, now you can push the results using fedpkg push or git push.

For each branch that you’d like to request a build for, switch using fedpkg switch-branch and run fedpkg build.

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 buildsystem will send you an email to report the failure and link you to the logs. Commit any needed changes to git, bump the spec release number and request a new build.

You should close it with resolution NEXTRELEASE or RAWHIDE, depending on where you built the package. The resolution field will appear after you set the status field to CLOSED.