Packaging

---

title: Packaging
updated_on: Fri Dec 16 13:13:12 ~~0500 2011\

\
h1. Packaging
\
The following are the lead packagers for the various aeolus components.
These are the engineers responsible for making sure their components are
tested and packaged correctly for Fedora at the end of every development
cycle

\
conductor~~ sseago\
configure - mmorsi\
imagefactory - imcleod\
aeolus-image - mtaylor \*\
aeolus-cli - mtaylor \*\
iwhd - jmeyering\
oz - clalance\
deltacloud - mfojtik\
audrey - JoeVLcek \*

-   needs fedora sponsorship

New packager guide
------------------

You will need to be a Fedora packager, traditionally you’d go through
the sponsorship process, but we are looking into adding some packagers
to specific components

All in all, make sure the following steps are done before hand

-   Create a FAS account
    [https://admin.fedoraproject.org/accounts](https://admin.fedoraproject.org/accounts)/
    -   Sign the CLA, upload a public rsa ssh key

-   yum install fedora-packager fedpkg
-   run ‘fedora-packager-setup’

Packaging Guide
---------------

After you have been added to the packagers group

-   get the latest SRPM of the package you will be updating, do a
    scratch build in koji
    -   koji build —scratch f16 <srpm>
    -   if this doesn’t succeed, you need to view the koji build (at the
        provided link) to figure out whats wrong

-   Submit package to bugzilla for review
-   fedpkg clone <name of your package>
    -   the default ‘master’ branch will correspond to rawhide

-   cd <name of your package>
-   fedpkg import <srpm>
-   verify the commit looks sane
-   git commit
    -   add a message like ’updating <package name> to <version>

-   git push
-   fedpkg build
-   fedpkg switch-branch f16
-   repeat process
    -   fedpkg import <srpm>
    -   verify
    -   git commit
    -   git push
    -   fedpkg build

-   finally navigate to bodhi
    [https://admin.fedoraproject.org/updates](https://admin.fedoraproject.org/updates)
    -   submit the update by clicking ‘new update’, typing the name of
        your component and selecting the build
    -   an update will automatically be pushed to fedora-testing
    -   it won’t be available for fedora updates for a week, unless it
        reaches the stable push karma
    -   set the karma lower (to 1 if you want) to allow for a quicker
        update (a karma of 1 means just one person will need to give it
        a thumbs up)
    -   when the karma is reached, log into bodhi and click ‘mark as
        stable’, you are now done!

Karma
-----

To give a package update karma, simply navigate to the update in bodhi
([https://admin.fedoraproject.org/updates)](https://admin.fedoraproject.org/updates)),
click ‘add a comment’, and then select ‘works for me’

Other Resources
---------------

-   [https://fedoraproject.org/wiki/Using\_git\_FAQ\_for\_package\_maintainers](https://fedoraproject.org/wiki/Using_git_FAQ_for_package_maintainers)
-   [http://fedoraproject.org/wiki/File:Fedora-submit-package.png](http://fedoraproject.org/wiki/File:Fedora-submit-package.png)
    (workflow diagram by mmorsi)