On Wed, May 23, 2012 at 5:05 PM, Jeremy Davis <jdavis4102(a)gmail.com> wrote:
I hope I picked the correct mailing list to ask these types of questions.
In my environment we are trying to setup a koji build system using the same
structure that you all use for the Fedora project. This involves using
fedpkg (modified for our environment) to import the SRPM into the SCM and
then tell koji to build. We have everything working with our environment but
have to do a couple of things manually. Mainly the SCM creation and adding a
tag for the package in koji before the user is allow to add their srpm to
the SCM and build with koji (get the error that it can't tag if a tag is not
created before hand). Once we create the SCM and add the tag into Koji
everything works as it should based on the documentation I have read.
My question is this. Do you by chance have any tools that automate the SCM
creation and koji tag adding? Is this how you all manage packages in Fedora?
Do you have to manually create SCM and koji tags when a user wants to add a
new package to Fedora? Any assistance you could provide would be greatly
Note: This is for an internal package build system for my company and will
only be used as such. I am willing to share what I have done as the fedpkg
will also be used to push the packages into our Spacewalk environment and
also push those packages to systems within Spacewalk (with some custom code
that I am adding to fedpkg and renaming that command to fit into our naming
Thank you for your time and have a great day!
I think the list for this is actually buildsys@, but for the sake of
being helpful, I'll answer here.
Currently, I run a koji server too, for a project called GoOSe Linux
and our site is horrible looking, please be
kind). To prepare any package for inclusion to koji, I've written a
component of our tool, called Skein, which is roughly based upon
fedpkg as well (https://github.com/gooseproject/skein
). The specific
functions I use are skein request, skein query and the most important,
Essentially, there are 3 basic things needed to build with koji. A
lookaside cache (a location in which to store the source tarball or
other large bits), a scm repository with at least the spec file and
any patches, and a way to tag the package in koji. Koji has an XML-RPC
api that is pretty extensive for this (koji list-api will help) but
essentially, when someone runs skein grant pkg-name, it creates the
directories for the lookaside cache, creates the github repository and
then tags the package in koji according to a configuration or passed
It was pretty simple to write, but feel free to grab the code and
reuse at your leisure. If you have any questions, please feel free to
email me off-list as well.