User:Mziaei1/eclipse/fedpkg

Fedora Package Process

This cheat sheet will demonstrate how to create a RPM package using eclipse Fedora Packager.

Create Account

If you are a new package maintainer:

• Create a new account on Fedora Account System (FAS)
  • Click on 'New account' and fill in the blanks.
  • After you create your account, please be sure to sign the CLA (if you click on the "My Account" link in the top right, you should see CLA: CLA Done).
  • Also you need to upload a public RSA SSH key. You need to use the matching private key to access Fedora machines via SSH
• Create an account in Red Hat bugzilla.
• Install the client tools
  • To build Packages for the Fedora Collection or EPEL, you need Koji.
  • You'll also need to generate a client side certificate at the Fedora Account System and save the file in ~/.fedora.cert, where fedpkg will look for it by default.
  • You can now use "koji" to try to build your RPM packages on platforms (e.g., PPC) or distributions you don't have. Note that you can test out builds ("scratch" builds) even when your package hasn't been approved and you don't have a sponsor. Here is a simple way to do a scratch build using koji on the command line.

Make a Package

• Make sure it is a new package. Check this list of existing packages.
• Create an RPM package:
  • Select "File->New->Other..." from the main menu. Choose "RPM->RPM Project", click "Next".
  • Input the "Project name". Click "Finish".
  • Right click on SPECS, select "New->Other...", choose "RPM->Specfile Based on a Template", click "Next".
  • Fill out the template or accept the default values and customize it based your package specifications.
    • You can also use RPM-stubby plug-in to create a spec-file stub.
  • To send your SRPM/Spec-file for review, select "File->Export" from the main munu, choose "RPM->Source/Binary RPM", click "Next".
  • Based on your requirements, select one or both options, click "Finish".
• Make sure it is a suitable package
  • Check Packaging Guidelines and Packaging Naming Guidelines to see if it meets the requirements
  • Read some other package submissions to learn about packaging and gain familiarity with the process and requirements. One way of doing this is to join the package-review@lists.fedoraproject.org mailing list.

(provide space to enter URL of hosted SRPM/.spec or scp to fedorapeople.org) and create review-request bug (using mylyn)

Submit For Review

• Join the mailing lists (introduce yourself)
• Upload your package
  • Upload your SRPM and SPEC files onto the Internet somewhere. This can be anywhere accessible by a URL.
  • If you need hosting space, please make a note of it in your ticket submission and someone will take care of you.
  • If you have already got a Fedora Account then you can use your storage at <user-name>.fedorapeople.org for this.
• Create your review request
  • Fill out this form at bugzilla.
  • Before submitting your request, be sure there’s not a previous request for the same package.
  • Make sure that you put the name of the package (excluding version and release numbers) in the 'Review Summary' field, along with a very brief summary of what the package is.
  • Put a description of your package (usually, this can be the same thing as what you put in the spec %description) in the 'Review Description' field.
  • Include the URLs to your SRPM and SPEC files.
  • If this is your first package, explain it and say that you need a sponsor.
• Watch the bugzilla report for feedback
  • Watch the Bugzilla report for your first package. You should get notifications of changes by email. Fix any blockers that the reviewer(s) point out.

Ready to Ship

Follow these steps after your package is approved by reviewers.

• Obtain member sponsorship (to check in and build your package)
  • you must separately obtain member sponsorship in order to check in and build your package. Sponsorship is not automatic and may require that you further participate in other ways in order to demonstrate your understanding of the packaging guidelines.
  • Key to becoming sponsored is to convince an existing sponsor-level member that you understand and follow the project's guidelines and processes.
  • See how to get sponsored into the packager group for more information.
• Add package to Source Code Management (SCM) system and Set Owner

When the package is approved by the reviewer, request a git module and branches with the SCM admin requests.

• Check out the empty module from SCM
  • Once you have the git module, checkout your module from git.
    • Select "import->Git->Projects from Fedora Git" and click on Next.
    • Input the name of the package in the "Package name".
  • It is probably a good idea to make a "git" toplevel directory, then check-out your files inside of that. (--Do we need this line?)

Update your SCM

• Import and commit your SRPM into master branch
  • Right click on your locally package made inside eclipse...--can be a new feature
• Build your package
• Submit your package as update in Bodhi
  • 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.
  • For doing this go to Fedora Packager -> Create New Bodhi Update
• Close the bugzilla account
  • If the package built successfully, you should close it as NEXTRELEASE.
• Add the package to the comp files
  • If appropriate for the package, make it available in "comps" files so that it can be selected during installation and included in yum's package group operations. See PackageMaintainers/CompsXml for more info.
• Enable Upstream Release Monitoring
  • Fedora has infrastructure available for monitoring new upstream releases of the software you are packaging. Refer to Upstream Release Monitoring for more details.