I'm using koji as a python package in my scripts. Usually I develop them
inside of a virtual environment. I do not use system packages in
Currently I'm not able to install koji and it dependencies inside
virtualenv easily. Having koji in PiPy would help me. That way I can
just specify it in my requirements.txt or in install_requires of my
setup.py. I *guess* one way to do that is to have setup.py in koji
code and add some extra steps as part of the release process to publish
What do you think about this?
For some time now I use my own setup.py. I guess it is not ready for PR
so I'd love to see comments on this as well:
 Among other reasons I'd like to have environment isolated from the
system as much as possible.
 I have never maintained package on PiPy.
We have a build tag named dist-el7-build that contains two external
repos: dist-el7-centos73, which contains the base OS packages for CentOS
7, and dist-el7-centos73-updates which contains updated packages for
CentOS 7. Normally, we would like the packages from
dist-el7-centos73-updates to take precedence since they're newer, but
not for a specific package, selinux-policy.
Is there a way I can keep selinux-policy from being brought in from
dist-el7-centos73-updates? I didn't see a way to do that by editing the
external repo definiton, so my idea is this:
1. Create a new tag named el7-updates that contains just the
dist-el7-centos73-updates external repo
2. Have dist-el7-build inherit from el7-updates, but use --pkg-filter to
somehow exclude selinux-policy; I'm not sure about that, though,
since I don't know if --pkg-filter is inclusive or exclusive
Would that work? Do you have better suggestions?
Mátyás (Mat) Selmeci
Open Science Grid Software Team / Center for High-Throughput Computing
University of Wisconsin-Madison Department of Computer Sciences
Today marks the ten year anniversary of the initial publication of Koji.
Koji grew out of Red Hat's internal Brew build system. It was initially
adopted in Fedora, but has since found use in many other places
including CentOS, Scientific Linux, Kolab, TomTom, and Amazon.
The past year or so has seen a pronounced increase in Koji activity.
Since we've moved to Pagure, it's become much easier for folks to
It's an exciting time as Koji grows to meet new challenges in building
Linux distributions! Thank you to everyone who has helped along the way
and to those who will help in the future!