From Fedora Project Wiki

(Fix wrong git commands. There is no "git commit -p"! Also, it's "git push" not "git pull" to push the results out to the repository!)
(Replace with link to Package Maintainer Docs at docs.fp.o)
Tag: Replaced
(42 intermediate revisions by 31 users not shown)
Line 1: Line 1:
{{admon/important|Contributors only!|This document is for existing Contributors only. If you do not already have a Fedora account or if this is your ''first'' Fedora package, you ''must'' follow the process documented in [[PackageMaintainers/Join]].}}
{{admon/warning |This page has been moved out of the wiki. The current version of this document is located at update your bookmarks.}}
This is a short version of the [[PackageMaintainers/Join]] document, streamlined to show how existing contributors can make new packages.
'''Step 1:''' Read the [[Packaging:Guidelines|  Packaging Guidelines]]  and [[Packaging:NamingGuidelines|  Package Naming Guidelines]] . Really. Be comfortable with them. <BR>
'''Step 2:''' Make a package.
* You should make sure that it is a new package. A list of existing packages in Fedora Packages is here:
* Some information on how to create an RPM package is in the [[PackageMaintainers/CreatingPackageHowTo| Creating Package HOWTO]]
* Make sure that your package meets the [[Packaging:Guidelines|  Packaging Guidelines]]  and [[Packaging:NamingGuidelines|  Package Naming Guidelines]]
* Be aware of ForbiddenItems and [[Packaging:ReviewGuidelines|  Package Review Guidelines]]  (they will be used during the package review)
'''Step 3:''' Upload your SRPM and SPEC files onto the internet somewhere. <BR>
* If you have already got a Fedora Account then you can use your storage at for this.
'''Step 4:''' Make sure you have a bugzilla account at <BR>
'''Step 5:''' Fill out this form:
* 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 here: [[Packaging:ReviewGuidelines|  Package Review Guidelines]]
'''Step 6:''' Watch the bugzilla report for your first package (you created this in step 5). Fix any blockers that the reviewer(s) point out. <BR>
'''Step 7:''' When the package is approved by the reviewer, request a git module and branches with the [[PackageMaintainers/Git_Admin_Requests|  Git admin requests]] . <BR>
'''Step 8:''' Checkout the git module (details [ here] )
* Once you have the git module, checkout your module from git.  Refer to
* It is probably a good idea to make a "git" toplevel directory, then check-out your files inside of that.
* If your package is named foobar, this is done with: fedpkg clone foobar
'''Step 9:''' Import your srpm
* Then you can import the approved SRPM into master branch by running <code> fedpkg import libfoo-x.x.x.src.rpm; git commit -m "Initial import (#nnnnnn)."</code> (where nnnnnn is your Bugzilla package review bug number).
* Obviously, replace nameofmy.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 master branch.
'''Step 10:''' You can now import the package to your branches too
* The quickest way to do this is to use <code>fedpkg switch-branch BRANCH</code> to switch the branch (where BRANCH can be "f13" and so on).
* Get the sources in.  One way is to copy the sources file, .gitignore file, .spec file and any patches from master to each branch. Also check if the Makefile exists and copy it if necessary. After that, <code>git add</code> all copied files. Alternatively, use <code>fedpkg import</code> as above.
* Once you've put the files in, commit them with: <code>git commit -m "Initial import (#nnnnnn)."</code> and push the results with <code>git push</code>.
'''Step 11:''' Request builds
* For each branch that you'd like to request a build for, switch using fedpkg switch-branch  and run: <code>fedpkg build</code>
* 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.
'''Step 12:''' Close the bugzilla ticket (assuming that the package built successfully)
* You should close it as NEXTRELEASE.
'''Step 13:''' If this package will be built for any version of Fedora that is already released please submit it for inclusion in the 'fedora-updates' repository for those versions of Fedora. See [[PackageMaintainers/UpdatingPackageHowTo#Submit_your_update_to_Bodhi|submitting your update to bodhi]]  for more details.<BR>
'''Step 14:''' Add the package to the [[PackageMaintainers/CompsXml|comps file(s)]] if appropriate.
We know that this process can be as clear as mud sometimes, we're always trying to make it better. If you run into any problems, or have any questions, please ask on fedora-devel-list. <BR>
There is a helpful [[Using_git_FAQ_for_package_maintainers|  git FAQ]]  which also includes instructions for making new releases.
[[Category:Package Maintainers]]

Latest revision as of 05:39, 15 September 2021

This page has been moved out of the wiki. The current version of this document is located at Please update your bookmarks.