From FedoraProject

Jump to: navigation, search


How to Build a Module in our Staging Infrastructure

The purpose of this document is to introduce you to messing around with the prototype tools the modularity working group has built.

This doc doesn't contain much explanation.. more of a step-by-step set of instructions to get you going. Read the other modularity pages for some insight on to what is going on and why. Ask in #fedora-modularity.

Prepare your environment

These steps are here just to make your workstation talk to our development environment. They are not part of the workflow.

If you're a provenpackager...

Then proceed to the next step. If you're not a provenpackager, then ask in #fedora-modularity for someone (threebean) to add you to the group in *staging* only. This is because you need rights to the dist-git repo for individual modules, but that's too difficult to maintain while we do all of this development. It is just easier to add people to stg provenpackagers for the time being.

Copy your 'fedpkg' config to your homedir, for editing.

   $ cp /etc/rpkg/fedpkg.conf ~/fedpkg-stg.conf

Customize that staging configuration file.

Repoint urls in that config to the staging environment.

   $ sed -i 's/pkgs.fedoraproject/pkgs.stg.fedoraproject/' ~/fedpkg-stg.conf

And add the following line to the end of the file

   ridaurl =

Get our patched copy of pyrpkg so fedpkg knows about modules.


   $ git clone
   $ cd rpkg

And modify your $PYTHONPATH to use this new location.

   $ export PYTHONPATH=$(pwd)/src/.:$PYTHONPATH

Build a module

This is the actual workflow.

Go and clone a test module...

   $ fedpkg -C ~/fedpkg-stg.conf co modules/testmodule
   $ cd testmodule

Try and build it

   $ fedpkg -C ~/fedpkg-stg.conf module-build

This should fail, because the module has already been built.

Try bumping the release in the yaml file, committing, pushing, and building again.

Look for the results

Look for your module in the rida API (not very interesting yet)

$ sudo dnf install httpie
$ http get --verify no

Look for your module in the BPO at

Look for your module in staging koji at

If anything goes wrong which it invariably will, look for logs at

Take a look at the other modules

We created repos for a number of them at

Some have been worked on but others we haven't gotten around to fleshing out yet. Still lots to do!